Closed
Bug 1610598
Opened 4 years ago
Closed 4 years ago
Windows / M(gl2e) sometimes exceeds its max-run-time
Categories
(Testing :: General, defect)
Tracking
(firefox74 fixed)
RESOLVED
FIXED
mozilla74
Tracking | Status | |
---|---|---|
firefox74 | --- | fixed |
People
(Reporter: gbrown, Assigned: gbrown)
References
Details
Attachments
(1 file)
As seen in bug 1589796:
https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=285721169&repo=mozilla-central&lineNumber=5027
https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=285701260&repo=autoland&lineNumber=5129
https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=285650564&repo=autoland&lineNumber=5103
Some runs are passing, but running in 28 or 29 minutes (max-run-time is 30 minutes).
Assignee | ||
Comment 1•4 years ago
|
||
Avoid intermittent test failures for exceeding max-run-time by increasing
mochitest-webgl2-ext max-run-time from 30 minutes to 45 minutes. This is immediately
an issue on Windows 7 (MinGW) debug, but other platforms are close to the 30 minute
limit, so we may as well increase it across the board.
Pushed by gbrown@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/d4c011e037e6 Increase max-run-time for mochitest-webgl2-ext; r=jmaher
Comment 3•4 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 4 years ago
status-firefox74:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla74
You need to log in
before you can comment on or make changes to this bug.
Description
•