Closed Bug 1062032 Opened 11 years ago Closed 8 years ago

Aurora B2G emulator nightlies are completely broken

Categories

(Firefox OS Graveyard :: General, defect)

Product:
Firefox OS Graveyard
Component:
General
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
blocker

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: ryanvm, Unassigned)

Details

Since today's uplift, B2G emulator dep builds (regular per-push builds) are running and passing tests. However, *nightly* builds are a sea of orange. So this mostly likely comes down to build config differences between dep builds and nightly builds. Aurora is closed until the cause of this is found and fixed.
The push below is an example of the bustage in question: https://tbpl.mozilla.org/?tree=Mozilla-Aurora&rev=5b8210dcf52a&jobname=b2g*.emulator The alternating green and orange on that push are the test runs from the dep builds (the green 'B') and the nightly builds (the green 'N'). Clearly something is seriously wrong with the test runs on the nightly build. And unfortunately, the next push with nightlies is showing the same failures.
Seeing a lot of this in the logs, is it relevant? [JavaScript Error: "NS_ERROR_XPC_CANT_MODIFY_PROP_ON_WN: Cannot modify properties of a WrappedNative" {file: "chrome://reftest/content/reftest-content.js" line: 145}]
I'm also seeing a bunch of TypeError foo is not a function: 59 INFO TEST-UNEXPECTED-FAIL | /tests/content/base/test/csp/test_bug949549.html | uncaught exception - TypeError: SpecialPowers.autoConfirmAppUninstall is not a function at http://mochi.test:8888/tests/content/base/test/csp/test_bug949549.html:57 427 INFO TEST-UNEXPECTED-FAIL | /tests/content/html/content/test/forms/test_input_email.html | uncaught exception - TypeError: element.matches is not a function at http://mochi.test:8888/tests/content/html/content/test/forms/test_input_email.html:46 389 INFO TEST-UNEXPECTED-FAIL | /tests/dom/canvas/test/test_canvas_path.html | uncaught exception - TypeError: p1.addPath is not a function at http://mochi.test:8888/tests/dom/canvas/test/test_canvas_path.html:354 478 INFO TEST-UNEXPECTED-FAIL | /tests/dom/datastore/tests/test_app_install.html | uncaught exception - TypeError: SpecialPowers.autoConfirmAppUninstall is not a function at http://mochi.test:8888/tests/dom/datastore/tests/test_app_install.html:57 481 INFO TEST-UNEXPECTED-FAIL | /tests/dom/datastore/tests/test_arrays.html | uncaught exception - TypeError: SpecialPowers.autoConfirmAppUninstall is not a function at http://mochi.test:8888/tests/dom/datastore/tests/test_arrays.html:99 484 INFO TEST-UNEXPECTED-FAIL | /tests/dom/datastore/tests/test_basic.html | uncaught exception - TypeError: SpecialPowers.autoConfirmAppUninstall is not a function at http://mochi.test:8888/tests/dom/datastore/tests/test_basic.html:99 487 INFO TEST-UNEXPECTED-FAIL | /tests/dom/datastore/tests/test_basic_worker.html | uncaught exception - TypeError: SpecialPowers.autoConfirmAppUninstall is not a function at http://mochi.test:8888/tests/dom/datastore/tests/test_basic_worker.html:99 which may be related to what kgrandon found.
Current master full flashed on my Flame also exposes a bunch of errors in logcat and for example I'm not able to place any call (but I can receive). There's a ton of weird behaviors :(
Nothing jumps out from comparing the build logs. Does a clobber build on Aurora display the same issues?
Assuming a non-nightly clobber build fails on Aurora, couldn't we just check out the merge point changesets form aurora and mozilla central and do a diff -qr /aurora /mozilla-central to sort this out?
Another thought, was there a recent change to the build tools used for b2g, like a mozconfig type change, that needs to be changed in Aurora?
Mozilla-central has: --enable-update-channel=emulator/2.2.0/default Aurora has: --enable-update-channel=emulator/2.1.0/default
That might explain issues on emulator builds, but it seems form other comments that there are issues with device builds as well.
(In reply to Ted Mielczarek [:ted.mielczarek] from comment #5) > Nothing jumps out from comparing the build logs. Does a clobber build on > Aurora display the same issues? Clobbering was the first thing we tried. Dep builds were still fine. (In reply to Bill Gianopoulos [:WG9s] from comment #6) > Assuming a non-nightly clobber build fails on Aurora, couldn't we just check > out the merge point changesets form aurora and mozilla central and do a diff > -qr /aurora /mozilla-central to sort this out? The uplift was yesterday. The nightlies that came off m-c yesterday morning were off nearly the exact same rev. The first busted Aurora nightlies were on the push immediately after the uplift. (In reply to Bill Gianopoulos [:WG9s] from comment #8) > Mozilla-central has: > > --enable-update-channel=emulator/2.2.0/default > > Aurora has: > > --enable-update-channel=emulator/2.1.0/default That would be expected, no? Aurora is v2.1 and m-c is v2.2 as of yesterday.
OK so if m-c was v2.1 pre uplift then that is NOT the issue.
Today's nightlies on Aurora are green off the same rev that was orange yesterday. That's comforting.
(In reply to Ryan VanderMeulen [:RyanVM UTC-4] from comment #12) > Today's nightlies on Aurora are green off the same rev that was orange > yesterday. That's comforting. Well, If we don't know what caused it, or what fixed it, I am not sure how that can be comforting.
I suppose this is the actual emulator build download which may be more useful? Essentially the same as above with 20140902154602 instead of nightly. I am not sure if this is useful or not yet, just making some notes. Broken: http://pvtbuilds.mozilla.org.proxxy.srv.releng.use1.mozilla.com/pub/mozilla.org/b2g/nightly/mozilla-aurora-emulator/latest/emulator.tar.gz Working: http://pvtbuilds.mozilla.org.proxxy.srv.releng.use1.mozilla.com/pub/mozilla.org/b2g/tinderbox-builds/mozilla-aurora-emulator/20140902154602/emulator.tar.gz
The emulator has been busted in a couple ways for me when invoked manually. The "back" widget at the top left of Settings and UITest does not work. The keyboard does not work in the Firefox Accounts flow. A lot of this in my log, which may or may not be relevant: [46976] ###!!! ASSERTION: old rule tree still referenced: 'Not Reached', file /Users/spenrose/repo/hg/mozilla-central/layout/style/nsStyleSet.cpp, line 1969
(In reply to Sam Penrose from comment #17) > [46976] ###!!! ASSERTION: old rule tree still referenced: 'Not Reached', > file /Users/spenrose/repo/hg/mozilla-central/layout/style/nsStyleSet.cpp, > line 1969 It's not relevant. I see that on my Nexus 5 which works fine.
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.