Constant timeouts of GU9 on treeherder

RESOLVED WORKSFORME

Status

Firefox OS
General
RESOLVED WORKSFORME
3 years ago
3 years ago

People

(Reporter: kgrandon, Assigned: gaye, NeedInfo)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Comment 2

3 years ago
Hmm, links seem to break when pasting unfortunately. Here is the output from a *bad* run: 

TEST-END | null | [emergency-call-test/unit/ice_contacts_test.js] ICE contacts bar Should create correct DOM Tapping a contact dials them took 2 ms
*** UTM:SVC TimerManager:notify - notified @mozilla.org/b2g/webapps-update-timer;1
*** UTM:SVC TimerManager:notify - notified @mozilla.org/addons/integration;1
*** UTM:SVC TimerManager:notify - notified @mozilla.org/extensions/blocklist;1
*** UTM:SVC TimerManager:notify - notified timerID: user-agent-updates-timer
*** UTM:SVC TimerManager:registerTimer - id: user-agent-updates-timer
[taskcluster] Task timeout after 1800 seconds. Force killing container.
[taskcluster] Unsuccessful task run with exit code: -1 completed in 1803.319
seconds


And the output from a *good* run: 

TEST-END | null | [emergency-call-test/unit/ice_contacts_test.js] ICE contacts bar Should create correct DOM Tapping a contact dials them took 2 ms
*~*~* Results *~*~*
passed: 282
failed: 0
todo: 0

  282 passing (769ms)

========= Finished run mkdir -p artifacts && ./bin/ci run unit-tests-in-b2g 2> artifacts/debug.log (results: 0, elapsed: 362 secs) (at 2015-02-07 00:03:37.423650) =========
[taskcluster] Successful task run with exit code: 0 completed in 531.458
seconds
(Reporter)

Comment 3

3 years ago
James/Gareth - this is happening on taskcluster. It appears that we run all of the tests, but timeout before outputting the *~*~* Results *~*~* section. Do you guys have any idea what might be causing this?

Can you link me to the code which outputs that *~*~* Results *~*~* section?

Thanks - this is one of the last issues before we can enable the GU suite for Autolander and use TC for gaia.
Flags: needinfo?(jlal)
Flags: needinfo?(gaye)
(Assignee)

Comment 4

3 years ago
Hrm I'm not super familiar with the differences between how things are run and how logging is handled between TC and buildbot.

https://github.com/mozilla-b2g/gaia/blob/master/bin/gaia_marionette_retry.js#L45 outputs the mocha epilogue right now
Flags: needinfo?(gaye)
(Assignee)

Comment 5

3 years ago
I can investigate with some TC hand-holding after I finish up the python crash reporter marionette-js-runner integration.
(Assignee)

Updated

3 years ago
Assignee: nobody → gaye
(Reporter)

Comment 6

3 years ago
Thanks for taking Gareth. Note: this is for unit tests, and not integration tests.
(Assignee)

Comment 7

3 years ago
Ohhh! Okay. I can still help out but the part that outputs the mocha epilogue is actually here https://github.com/mozilla-b2g/mocha-tbpl-reporter/blob/master/lib/tbpl.js#L58 (for the integration tests the retry script parses and aggregates the logs from individual test file runs)
(Reporter)

Comment 8

3 years ago
I think James is currently working on this one in another bug. Likely bug 1146302.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.