Closed Bug 1160010 Opened 10 years ago Closed 7 years ago

Intermittent Android mochitest/reftest No tests run or test summary not found due to an | application ran for longer than allowed maximum time

Categories

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

Product:
Firefox for Android Graveyard
Component:
Testing
Platform:
ARM
Android
Type:
defect

Tracking

(firefox40 affected)

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox40 --- affected

People

(Reporter: philor, Assigned: gbrown)

References

Details

(Keywords: intermittent-failure, Whiteboard: [fennec-scouting])

No description provided.
Summary: Intermittent Android 4.3 reftest No tests run or test summary not found due to an | application ran for longer than allowed maximum time → Intermittent Android 2.3/4.3 reftest No tests run or test summary not found due to an | application ran for longer than allowed maximum time
This is spiking badly recently, mostly in M9.
Summary: Intermittent Android 2.3/4.3 reftest No tests run or test summary not found due to an | application ran for longer than allowed maximum time → Intermittent Android 2.3/4.3 mochitest/reftest No tests run or test summary not found due to an | application ran for longer than allowed maximum time
Android 2.3 mochitest-9 is now nearly perma-fail.
Depends on: 1156425
Depends on: 1216226
Depends on: 1216304
Only some of the recent failures reported here are "application ran for longer than allowed maximum time". Of those, most are reftests and most are debug, but there is little other commonality, and failures seem random: A job will run in 45 minutes, the next push will time-out (more than 2x as long), the next will run in 45 minutes. Logs suggest the slow-down is consistent across the test: The first 10% and the last 10% of the test are equally slow. Broadly, I have 2 theories: A random bug in gecko saps cpu or memory on some test runs, or, some aws instances are slower than others. Regarding aws, I wonder if bug 1217863 might be related (running low on disk space might slow down the emulator?)
Android 4.3 Debug mochitest-13 times out on mozilla-beta (Firefox 43). See bug 1208920 and discussion starting at https://bugzilla.mozilla.org/show_bug.cgi?id=1188545#c76...
Depends on: 1208920
In addition to bug 1208920 and mis-stars, there are several very-low-frequency failures accumulated here: - OOM (associated with system backup processing?) - crash on startup - crash on shutdown - unusually slow test run -> job timeout, as in Comment 518
Depends on: 1233311
Android 4.3 API11+ debug R(34) seems to be perma-failing, and is getting starred as this bug. See https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&tochange=10d4e8736dbb&fromchange=52b41d0b5edb&filter-searchStr=Reftest%20R%28R34%29 for example. I triggered the job on the two pushes between where it was passing and where it started failing to narrow down the regression. Don't know if the "Add new jobs" thing in TH is working yet.
Depends on: 1245630
Depends on: 1245884
The number of 4.3 opt/debug crashtest chunks was recently increased - that should avoid a few of these failures.
Summary: Intermittent Android 2.3/4.3 mochitest/reftest No tests run or test summary not found due to an | application ran for longer than allowed maximum time → Intermittent Android mochitest/reftest No tests run or test summary not found due to an | application ran for longer than allowed maximum time
Bulk assigning P3 to all open intermittent bugs without a priority set in Firefox components per bug 1298978.
Priority: -- → P3
Whiteboard: [fennec-scouting]
No failures here for many weeks.
Assignee: nobody → gbrown
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
If this recurs, I'd prefer a new bug was opened, rather than re-opening this one (too much irrelevant history here).
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.