Closed Bug 1295175 Opened 8 years ago Closed 8 years ago

Intermittent mobile/android/tests/browser/chrome/test_awsy_lite.html | Test timed out.

Categories

(Firefox for Android Graveyard :: Testing, defect, P1)

defect

Tracking

(firefox51 fixed)

RESOLVED FIXED
Firefox 51
Tracking Status
firefox51 --- fixed

People

(Reporter: intermittent-bug-filer, Assigned: gbrown)

Details

(Keywords: intermittent-failure)

We previously had trouble with "330 seconds without output" because of log buffering, but that's fixed now. It looks like this test can complete in less than 250 seconds, but sometimes takes twice that long. Is that just variance in page load times?
Assignee: nobody → gbrown
Priority: -- → P1
(In reply to Geoff Brown [:gbrown] from comment #1)
> We previously had trouble with "330 seconds without output" because of log
> buffering, but that's fixed now. It looks like this test can complete in
> less than 250 seconds, but sometimes takes twice that long. Is that just
> variance in page load times?

Android 4.3 opt mochitest-chrome runs on a faster instance type on taskcluster. On TC, awsy test time is about 250 seconds, but on buildbot it is 500+ seconds, timing out on slightly slower runs.
Pushed by gbrown@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/fe333162679e
Increase timeout for android mochitest-chrome test_awsy_lite; r=me
https://hg.mozilla.org/mozilla-central/rev/fe333162679e
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 51
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.