Closed Bug 1088708 Opened 10 years ago Closed 9 years ago

Intermittent testOSLocale | GeckoEventExpecter - blockForEvent timeout: Gecko:DelayedStartup

Categories

(Firefox for Android Graveyard :: Testing, defect)

Product:
Firefox for Android Graveyard
Component:
Testing
Platform:
x86
Android
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: cbook, Unassigned)

References

(
URL
)

Details

(Keywords: intermittent-failure, Whiteboard: [test disabled on Android x86]) 

Android 4.2 x86 Emulator mozilla-inbound opt test androidx86-set-4

https://treeherder.mozilla.org/ui/logviewer.html#?job_id=3285649&repo=mozilla-inbound

07:31:35 WARNING - TEST-UNEXPECTED-FAIL | testOSLocale | GeckoEventExpecter - blockForEvent timeout: Gecko:DelayedStartup
This implies that Fennec didn't successfully start within some long duration (30 seconds? 60?), that it was already started by the time Robocop ran (which should not be the case), or that our testing event expecter didn't work correctly.

This is the first wait in the test, so I feel quite comfortable not pointing the finger at the test itself!
Component: General → Testing
Something in infra-land made this go perma-fail across all trees today. Disabled while gbrown investigates.
https://hg.mozilla.org/mozilla-central/rev/c4dad0529749
Assignee: nobody → ryanvm
Whiteboard: [test disabled on Android x86]
Assignee: ryanvm → nobody
Comparing a failed logcat:

http://mozilla-releng-blobs.s3.amazonaws.com/blobs/fx-team/sha512/22be5d49282e83eb925b1a6f6c8513922b51507996ee97e03d3788b728abcf05acbc06511274847245623e8a52bbef7795a92e8e8bc1cdb400d333dd32643c24

to an older success:

http://mozilla-releng-blobs.s3.amazonaws.com/blobs/mozilla-central/sha512/1ed822de432417a335740e7f4937bfc2562583cb17c81e3b0a2d0340580cd994f2450f32867daf02b53db87c1cdb8603f4ee2a112b0f0b8259276aed0d8a32f5

what I note is that BaseTest.setUp() took longer to run in the failure case: it looks likely that the failed testOSLocale started waiting for DelayedStartup after the event was already sent.

I am not sure what would change the timing of BaseTest.setUp(). I particularly don't see any recent changes on aurora/beta that might be related. For infra, maybe the hostutils update? Also, setUp() does an http get...so there is a dependency on network performance (between the device and the test slave).


It would be nice if blockForDelayedStartup had a guard against event racing, similar to what is in blockForGeckoReady.
In bug 1094649 I tried using blockForDelayedStartup in more tests (all JavascriptTest tests) and hit this bug frequently on x86 - https://treeherder.mozilla.org/#/jobs?repo=try&revision=5e0289b50633.
See Also: → 1094649
Robocop tests are no longer scheduled on the Android x86 emulator -- bug 1132209.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.