Closed
Bug 1592115
Opened 6 years ago
Closed 6 years ago
raptor-tp6-N-firefox-cold-e10s tasks on windows10-64-ref-hw-2017 sometimes exceed their max-run-time
Categories
(Testing :: Raptor, defect, P1)
Tracking
(firefox72 fixed)
RESOLVED
FIXED
mozilla72
| Tracking | Status | |
|---|---|---|
| firefox72 | --- | fixed |
People
(Reporter: gbrown, Assigned: gbrown)
References
Details
Attachments
(1 file)
https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=273235141&repo=mozilla-central&lineNumber=3862
https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=273235242&repo=mozilla-central&lineNumber=3108
https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=273186931&repo=mozilla-central&lineNumber=4024
https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=273144395&repo=mozilla-central&lineNumber=3831
None of these seem to be hung: they might succeed if they just had more time.
Normal green runs are in the 20 - 30 minute range; current max-run-time is 40 minutes.
| Assignee | ||
Comment 1•6 years ago
|
||
Avoid intermittent task timeouts.
Thanks, Geoff. When you get a chance, would you link to try runs, with the timeout bumped?
| Assignee | ||
Comment 3•6 years ago
|
||
Updated•6 years ago
|
Priority: -- → P1
Pushed by gbrown@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/c569d854b516
Increase max-run-time for some raptor tests on windows10-64-ref-hw-2017; r=perftest-reviewers,stephendonner,sparky
Comment 5•6 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox72:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla72
Comment 6•6 years ago
|
||
| bugherder landing | ||
You need to log in
before you can comment on or make changes to this bug.
Description
•