Closed
Bug 1023001
Opened 10 years ago
Closed 10 years ago
Gaia unit test perma-hanging ("timed out after 1760 seconds of no output") on Trunk
Categories
(Firefox OS Graveyard :: Gaia, defect)
Tracking
(firefox31 unaffected, firefox32 unaffected, firefox33 fixed, firefox-esr24 unaffected, b2g-v1.3 fixed, b2g-v1.3T fixed, b2g-v1.4 fixed, b2g-v2.0 fixed, b2g-v2.1 fixed)
RESOLVED
FIXED
2.0 S4 (20june)
Tracking | Status | |
---|---|---|
firefox31 | --- | unaffected |
firefox32 | --- | unaffected |
firefox33 | --- | fixed |
firefox-esr24 | --- | unaffected |
b2g-v1.3 | --- | fixed |
b2g-v1.3T | --- | fixed |
b2g-v1.4 | --- | fixed |
b2g-v2.0 | --- | fixed |
b2g-v2.1 | --- | fixed |
People
(Reporter: RyanVM, Assigned: jgriffin)
References
Details
(Keywords: intermittent-failure)
Attachments
(2 files)
It appears to have started with the version bump on m-c, but the timing could also be pointing to something in today's reconfig. I have retriggers going on earlier pushes to hopefully help narrow it down. Tests are passing fine on Aurora32. Trunk trees are currently closed.
https://tbpl.mozilla.org/php/getParsedLog.php?id=41392923&tree=Mozilla-Central
b2g_ubuntu64_vm mozilla-central opt test gaia-unit on 2014-06-09 15:51:27 PDT for push 4bf5e8d7c440
slave: tst-linux64-spot-876
16:00:52 INFO - starting WebSocket Server
16:00:52 INFO - Xlib: extension "RANDR" missing on display ":0".
16:00:53 INFO - 1402354853374 Marionette INFO marionette enabled via build flag and pref
16:00:53 INFO - 1402354853606 Marionette INFO marionette-server.js loaded
16:00:53 INFO - 1402354853651 Marionette INFO Listening on port 2828
16:00:53 INFO - 1402354853652 Marionette INFO Marionette server ready
16:00:53 INFO - System JS : WARNING resource://gre/modules/Preferences.jsm:36 - mutating the [[Prototype]] of an object will cause your code to run very slowly; instead create the object with the correct initial [[Prototype]] value using Object.create
16:00:53 INFO - Identity SignInToWebsiteController: persona uri = https://firefoxos.persona.org
16:00:57 INFO - ###################################### forms.js loaded
16:00:57 INFO - ############################### browserElementPanning.js loaded
16:00:57 INFO - ######################## BrowserElementChildPreload.js loaded
16:00:57 INFO - *** UTM:SVC TimerManager:registerTimer - id: user-agent-updates-timer
16:00:57 INFO - ############ ErrorPage.js
16:00:58 INFO - Xlib: extension "RANDR" missing on display ":0".
16:00:58 INFO - ###################################### forms.js loaded
16:00:58 INFO - ############################### browserElementPanning.js loaded
16:00:58 INFO - ######################## BrowserElementChildPreload.js loaded
16:02:53 INFO - *** UTM:SVC TimerManager:notify - notified @mozilla.org/b2g/webapps-update-timer;1
16:04:53 INFO - *** UTM:SVC TimerManager:notify - notified @mozilla.org/addons/integration;1
16:06:53 INFO - *** UTM:SVC TimerManager:notify - notified @mozilla.org/extensions/blocklist;1
16:08:53 INFO - *** UTM:SVC TimerManager:notify - notified timerID: user-agent-updates-timer
16:08:53 INFO - *** UTM:SVC TimerManager:registerTimer - id: user-agent-updates-timer
16:38:14 INFO - Automation Error: mozprocess timed out after 1760 seconds running ['/builds/slave/test/build/venv/bin/python', '-u', '/builds/slave/test/gaia/tests/python/gaia-unit-tests/gaia_unit_test/main.py', '--binary', '/builds/slave/test/build/application/b2g/b2g-bin', '--profile', '/builds/slave/test/gaia/profile-debug', '--symbols-path', 'https://ftp-ssl.mozilla.org/pub/mozilla.org/b2g/tinderbox-builds/mozilla-central-linux64_gecko/1402323097/en-US/b2g-33.0a1.en-US.linux-x86_64.crashreporter-symbols.zip']
16:38:14 ERROR - timed out after 1760 seconds of no output
16:38:14 ERROR - Return code: -9
16:38:14 INFO - TinderboxPrint: gaia-unit-tests: <em class="testfail">T-FAIL</em>
16:38:14 ERROR - Tests exited with return code -9: harness failures
16:38:14 ERROR - # TBPL FAILURE #
Assignee | ||
Comment 1•10 years ago
|
||
The problem is that --runapp is broken; the build isn't even launching the TestAgent app.
Assignee | ||
Comment 2•10 years ago
|
||
Moving to General since this isn't a TestAgent issue.
Component: Gaia::TestAgent → General
Reporter | ||
Comment 3•10 years ago
|
||
Reporter | ||
Comment 4•10 years ago
|
||
I retriggered a Gaia unit test job on a previously-green run and it was also green. Right now, the only common theme I can find among when the failures started is the version bump.
Comment 5•10 years ago
|
||
Usually if I got this sort of issue in Thunderbird I would be looking at min/max versions for test extensions - is there something similar for Test Agent? I have no idea where that code is.
Assignee | ||
Comment 6•10 years ago
|
||
(In reply to Mark Banner (:standard8) from comment #5)
> Usually if I got this sort of issue in Thunderbird I would be looking at
> min/max versions for test extensions - is there something similar for Test
> Agent? I have no idea where that code is.
Bingo, Mark wins the prize.
There are several extensions which are used in the debug profile at https://github.com/mozilla-b2g/gaia/tree/master/tools/extensions; several of them contain maxVersion 32.0, so the recent version bump broke them.
Assignee | ||
Comment 7•10 years ago
|
||
Assignee | ||
Comment 8•10 years ago
|
||
Reporter | ||
Comment 9•10 years ago
|
||
For posterity, this was a regression from bug 861424.
Depends on: 861424
Reporter | ||
Comment 10•10 years ago
|
||
And we're green again. Will merge b2g-inbound around and re-open the trees shortly.
Assignee: nobody → jgriffin
Status: NEW → RESOLVED
Closed: 10 years ago
status-firefox31:
--- → unaffected
status-firefox32:
--- → unaffected
status-firefox33:
--- → fixed
status-firefox-esr24:
--- → unaffected
Resolution: --- → FIXED
Target Milestone: --- → 2.0 S4 (20june)
Comment 11•10 years ago
|
||
More like generic Gaia issue since there isn't a specific component for DEBUG=1 add-ons.
Component: General → Gaia
Comment 12•10 years ago
|
||
Ryan, does it make sense to land this on the various still worked-on branches? At least v2.0 (if it was after the merge), v1.4, v1.3t.
(I think it's useful, I usually use the same Firefox to run my local tests even if Travis should use the correct one..)
Flags: needinfo?(ryanvm)
Reporter | ||
Comment 13•10 years ago
|
||
Seems unlikely that we're ever going to bump the Gecko rev past 32 on those branches, so what would it accomplish?
Flags: needinfo?(ryanvm)
Reporter | ||
Comment 14•10 years ago
|
||
But honestly, I have no opinion.
Assignee | ||
Comment 15•10 years ago
|
||
If you're going to use older branches with the latest Firefox, then yes, it makes sense to merge these to older branches.
Comment 16•10 years ago
|
||
Yes, that's what I meant: I usually use the same nightly to run the test agent on the branches. Moreover, since we moved the test-agent files, I have to regenerate a profile when I switch to v1.3t (not sure about v1.4), so the "bad" httpd would definitely be in the profile.
Ryan, can you do the uplift then?
Flags: needinfo?(ryanvm)
Reporter | ||
Comment 17•10 years ago
|
||
v2.0: https://github.com/mozilla-b2g/gaia/commit/d5115052333dabd09bee1d60fd752717f2211c11
v1.4: https://github.com/mozilla-b2g/gaia/commit/d1cf95dc5e8b2f52148487291318542f1396608e
v1.3: https://github.com/mozilla-b2g/gaia/commit/51dde56948192d920a2f888f5528ae73ee97c32d
Will auto-merge to v1.3t from v1.3.
status-b2g-v1.3:
--- → fixed
status-b2g-v1.3T:
--- → affected
status-b2g-v1.4:
--- → fixed
status-b2g-v2.0:
--- → fixed
status-b2g-v2.1:
--- → fixed
Flags: needinfo?(ryanvm)
Reporter | ||
Updated•10 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•