Closed Bug 1433163 Opened 6 years ago Closed 6 years ago

Android 4.3 opt R18 (and debug R35 and others) sometimes runs too long / times out

Categories

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

Product:
Firefox for Android Graveyard
Component:
Testing
Type:
enhancement

Tracking

(firefox60 fixed)

Status:
RESOLVED FIXED
Milestone:
Firefox 60
Tracking Flags:
Tracking Status
firefox60 --- fixed

People

(Reporter: gbrown, Assigned: gbrown)

References

Details

Attachments

(1 file)

run android opt and debug reftests in more chunks
641 bytes, patch
jmaher
: review+
Details | Diff | Splinter Review 
      No description provided.
On trunk, Android opt R18 is currently the longest-running Android opt R chunk, typically running in 65-75 minutes. Failures occur after 90 minutes.
I see multiple instances of:

REFTEST WARNING | [CONTENT] MozInvalidateEvent didn't invalidate

even in successful runs.
Priority: -- → P1
Debug reftest-35 seems to have the same trouble, running more-or-less the same tests.
Summary: Android 4.3 opt R18 sometimes runs too long / times out → Android 4.3 opt R18 (and debug R35) sometimes runs too long / times out
As seen from the dups, most of the current "application ran for longer" failures are in Android opt R18 or Android debug 35, but there are also a handful of current failures in other reftest chunks. I think we just need more chunks.
As far as I can tell, we're just running more and more reftests, pushing our Android run times over our limits. This should give us just a little breathing room.
Attachment #8951600 - Flags: review?(jmaher)
Comment on attachment 8951600 [details] [diff] [review]
run android opt and debug reftests in more chunks

Review of attachment 8951600 [details] [diff] [review]:
-----------------------------------------------------------------

oh, this is painful- 56 chunks!
Attachment #8951600 - Flags: review?(jmaher) → review+
See Also: → 1412953
Pushed by gbrown@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/b2fe34d6f8a0
Increase android reftest test chunks; r=jmaher
It looks like those tests moved to the start of a chunk. I suppose they rely on earlier tests to set up state?

It's just a 1 pixel difference and most of those tests are already fuzzy-if'd for non-Android, so I might handle with a new fuzzy-if(Android).
Depends on: 1439115
Flags: needinfo?(gbrown)
Summary: Android 4.3 opt R18 (and debug R35) sometimes runs too long / times out → Android 4.3 opt R18 (and debug R35 and others) sometimes runs too long / times out
Pushed by gbrown@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/4d953971506f
Increase android reftest test chunks; r=jmaher
https://hg.mozilla.org/mozilla-central/rev/4d953971506f
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox60: affected → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 60
New occurrence:
https://treeherder.mozilla.org/logviewer.html#?job_id=195731358&repo=autoland
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to Andrei Ciure[:andrei_ciure_] from comment #56)
> New occurrence:
> https://treeherder.mozilla.org/logviewer.html#?job_id=195731358&repo=autoland

This was a slow-running Android/debug R41 that hit "application ran for longer than allowed maximum time" after about 110 minutes. These jobs typically run in about 75 minutes currently, so I think there is no action to take here; this was just a slow aws instance - basically bug 1321605. (I don't want to dup it to 1321605, since the earlier instances were addressed by the landed patch.)
Status: REOPENED → RESOLVED
Closed: 6 years ago → 6 years ago
Resolution: --- → FIXED
See Also: → 1321605
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: