Closed
Bug 852543
Opened 11 years ago
Closed 11 years ago
B2G desktop builds failing during make check on m-c
Categories
(Firefox OS Graveyard :: General, defect)
Firefox OS Graveyard
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: RyanVM, Assigned: fabrice)
References
Details
Attachments
(1 file)
2.54 KB,
patch
|
benjamin
:
review+
|
Details | Diff | Splinter Review |
Hiding them (again) for now... https://tbpl.mozilla.org/php/getParsedLog.php?id=20825258&tree=Firefox XPCOM_DEBUG_BREAK=stack-and-abort /builds/slave/m-cen-osx64_g-0000000000000000/build/obj-firefox/dist/bin/run-mozilla.sh \ ../../dist/bin/TestRegistrationOrder "/builds/slave/m-cen-osx64_g-0000000000000000/build/xpcom/tests/regorder"; Running RegistrationOrder tests... TEST-PASS | TestRegular TEST-UNEXPECTED-FAIL | TestJar FAILED - cannot create extension service TEST-PASS | RegTestOrderC Finished running RegistrationOrder tests.
Reporter | ||
Comment 1•11 years ago
|
||
Adding some XPCOM peers to the party. This needs an owner, it's blocking B2G desktop builds from running on m-c and inbound.
Severity: normal → critical
Comment 2•11 years ago
|
||
Is extension2.jar present and has the same/correct contents as in other builds?
Reporter | ||
Comment 3•11 years ago
|
||
How would I tell? As best I can tell, those tests don't get packaged? http://ftp.mozilla.org/pub/mozilla.org/b2g/tinderbox-builds/mozilla-central-win32_gecko/1363736354/
Comment 4•11 years ago
|
||
extension2.jar is part of the source code (http://mxr.mozilla.org/mozilla-central/source/xpcom/tests/regorder/extension2.jar) I don't know how the B2G config differs from a regular config... perhaps the source is not at the normal expected location?
Reporter | ||
Comment 5•11 years ago
|
||
These are builds off m-c and inbound, so extension2.jar is in the same place.
Reporter | ||
Comment 6•11 years ago
|
||
FWIW, we don't run make check on the b2g18 branches, so it's possible that this is broken there too and we just haven't known about it.
Comment 7•11 years ago
|
||
Yeah, I didn't mean that the source location was different, but perhaps the location of the entire B2G source tree is different?
Reporter | ||
Comment 8•11 years ago
|
||
AFAICT, these builds use the regular m-c source tree with Gaia cloned into $topsrcdir/gaia Andreas, can you suggest someone who could help debug this?
Flags: needinfo?(gal)
Reporter | ||
Comment 9•11 years ago
|
||
So, checktests were disabled on purpose for the b2g18 branches in bug 821401 comment 20. Unfortunately, nobody ever followed up on fixing said tests so that we could enable them again. So here we are. Are we going to disable our way to victory again or can we look into what it takes to get this fixed and these tests enabled?
Flags: needinfo?(jhford)
Assignee | ||
Comment 10•11 years ago
|
||
I can reproduce on a linux build also, I'll dig into that.
Assignee: nobody → fabrice
Assignee | ||
Comment 11•11 years ago
|
||
Kyle, the patch is in the binary jar, but is just applying there the same change as the one at: https://hg.mozilla.org/mozilla-central/diff/5ce71981e005/xpcom/tests/regorder/extension/extComponent.js
Attachment #727906 -
Flags: review?(khuey)
Updated•11 years ago
|
Attachment #727906 -
Flags: review?(khuey) → review+
Assignee | ||
Comment 12•11 years ago
|
||
http://hg.mozilla.org/integration/mozilla-inbound/rev/7f4e825f7c04
Comment 13•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/7f4e825f7c04
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Reporter | ||
Updated•11 years ago
|
Flags: needinfo?(jhford)
Flags: needinfo?(gal)
You need to log in
before you can comment on or make changes to this bug.
Description
•