test-android-em-4.3-arm7-api-16/debug-xpcshell-1proc-7 exceeding max-run-time
Categories
(Testing :: General, defect)
Tracking
(firefox68 fixed)
| Tracking | Status | |
|---|---|---|
| firefox68 | --- | fixed |
People
(Reporter: gbrown, Assigned: gbrown)
References
(Blocks 1 open bug, Regression)
Details
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=246407676&repo=mozilla-inbound&lineNumber=2171
https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=246426549&repo=autoland&lineNumber=2202
https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=246477782&repo=autoland&lineNumber=2186
https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=246830923&repo=autoland&lineNumber=2232
|
Assignee | |
Comment 1•6 years ago
|
||
Android 4.3/debug max-run-time is 7200 seconds: 120 minutes.
Android 4.3/opt xpcshell is okay, all chunks.
Android 4.3/debug xpcshell chunks other than 7 are okay -- typically running in less than 60 minutes.
|
|
Assignee | |
Comment 2•6 years ago
|
||
Android 4.3/debug xpcshell-7 has an abnormally high duration -- 2x other chunks.
|
|
Assignee | |
Comment 3•6 years ago
|
||
Android 4.3/debug xpcshell-7 began running >110 minutes when we changed from 12 test chunks to 8: bug 1548160.
|
|
Assignee | |
Comment 4•6 years ago
|
||
These chunks are quite out of balance: Probably there are some very long running
tests in xpcshell-7 with 8 chunks. Even so, I think the easiest way to avoid timeouts
is to return to 12 chunks.
|
||
Comment 6•6 years ago
|
||
| bugherder | ||
|
||
Updated•3 years ago
|
Description
•