Closed Bug 1143380 Opened 10 years ago Closed 9 years ago

Intermittent "marionette.errors.TimeoutException: TimeoutException: timed out waiting for emulator to start" or " mozrunner.errors.TimeoutException: timed out waiting for emulator to start" errors on B2G mochitest runs

Categories

(Testing :: General, defect, P1)

ARM
Gonk (Firefox OS)
defect

Tracking

(firefox45 fixed, firefox46 fixed)

RESOLVED FIXED
mozilla46
Tracking Status
firefox45 --- fixed
firefox46 --- fixed

People

(Reporter: philor, Assigned: edgar)

References

Details

(Keywords: intermittent-failure)

Attachments

(1 file)

+++ This bug was initially created as a clone of Bug #989048 +++ Nothing like it was in the glory days when failing to properly start the Linux host was making them constantly fail, but the bug existed before that problem, and still exists after it.
This bug is very important and it makes many mochitests hidden on B2G KK Emulator x86 opt.
Severity: normal → critical
Priority: -- → P1
Not just mochitests, and not just "many" of them: it's infra, it has nothing to do with what chunk or which suite, so I've hidden the rest of the mochitests and the crashtests, since they are all exactly equally affected.
Assignee: nobody → tzimmermann
Status: NEW → ASSIGNED
Depends on: 1231805
Unassigning myself as the problem will be fixed by bug 1231805.
Assignee: tzimmermann → nobody
Status: ASSIGNED → NEW
We still see this issue on treeherder after bug 1231805 is landed. And I cannot reproduce on my local environment. So I added some log in mozrunner to debug this, I found that sometimes testing infra takes more than 60s to launch emulator [1]. I have no idea why sometimes it takes so long, maybe because the infra is too busy or overloaded at that time. And I didn't see this error any more on my try pushes [2] with increasing the timeout value to 180s. [1] https://treeherder.mozilla.org/logviewer.html#?job_id=14847494&repo=try#L695 [2] https://treeherder.mozilla.org/#/jobs?repo=try&revision=3779955620ed&exclusion_profile=false&group_state=expanded
Assignee: nobody → echen
Attachment #8701837 - Flags: review?(ahalberstadt) → review+
Comment on attachment 8701837 [details] MozReview Request: Bug 1143380 - [mozrunner] Increase timeout value for waiting emulator to start. r=ahal https://reviewboard.mozilla.org/r/29033/#review26157 Thanks for digging into this and testing it out! ::: testing/mozbase/mozrunner/mozrunner/devices/emulator.py:121 (Diff revision 1) > + # increas timeout value to 180s. Please see bug 1143380. nit: increase
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla46
(In reply to Phil Ringnalda (:philor) from comment #643) > Not just mochitests, and not just "many" of them: it's infra, it has nothing > to do with what chunk or which suite, so I've hidden the rest of the > mochitests and the crashtests, since they are all exactly equally affected. It seems "timed out waiting for emulator to start" isn't happening any more, could we unhide the tests back? Thank you.
Flags: needinfo?(philringnalda)
https://treeherder.mozilla.org/#/jobs?repo=b2g-inbound&fromchange=f2864958c3c7&filter-tier=1&exclusion_profile=false&filter-searchStr=kk%20emulator&selectedJob=3718789 - those tests? Multiple permaorange and near-permaoranges in the mochitests, and the crashtests hang far too frequently, looking to be a different test pretty much every time so it's not a matter of just disabling a test or two, and at least fairly frequently the forced crash because of the hang is in nsDisplayBackgroundColor::GetOpaqueRegion looking like there's some platform-specific problem with it.
Flags: needinfo?(philringnalda)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: