Intermittent win 2012 [taskcluster:error] Task aborted - max run time exceeded
Categories
(Firefox Build System :: General, defect, P5)
Tracking
(Not tracked)
People
(Reporter: intermittent-bug-filer, Unassigned)
References
Details
(Keywords: in-triage, intermittent-failure)
Updated•7 years ago
|
| Comment hidden (Intermittent Failures Robot) |
Comment 2•7 years ago
|
||
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
Comment 17•6 years ago
|
||
Over the last 7 days this bug has 62 failures. These happen on windows2012-aarch64, windows2012-64, windows2012-32.
Here is the latest failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=231052566&repo=autoland&lineNumber=91029
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
Comment 22•6 years ago
|
||
This spike in timeouts has receded, we will re-evaluate if it occurs again if the max runtime needs to increase or the instance type needs to be changed.
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
Comment 27•6 years ago
|
||
Over the last 7 days there are 33 failures present on this bug. These happen on windows2012-aarch64, windows2012-64
Here is the most recent log example: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=239105056&repo=mozilla-central&lineNumber=38867
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
Comment 30•6 years ago
|
||
Looking at the most recent failures these are tending to be on trees where opt builds are pgo (beta, esr), or other random task timeouts.
We should up the timeout for these cases, but I don't think it's urgent given the recent frequency, and our solution here will change once the shippable configuration rides the trains.
Updated•6 years ago
|
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
Comment 35•6 years ago
|
||
This got frequent again on beta (and in central-as-beta simulations), failing 3 runs in a row or more: https://treeherder.mozilla.org/#/jobs?repo=mozilla-beta&searchStr=windows%2C2012%2Copt%2Cbuild-win32%2Fopt%2C%28b%29&fromchange=1f2cf02d4beba08f432cb2a6fabb3d20a6a59ba9&tochange=2f46b19ec841c939b84fa40be8b326a11141e6da&selectedJob=248134594
Updated•6 years ago
|
| Comment hidden (Intermittent Failures Robot) |
Comment 37•6 years ago
|
||
Looking at those retriggers we're timing out consistently on certain instance types. We're doing pgo builds here with the opt build configuration. We should be able to bump the max runtime to what the pgo builds have (3 hours instead of 2) on this branch to avoid this.
Comment 38•6 years ago
|
||
We did that increase for beta 68 yesterday: https://hg.mozilla.org/releases/mozilla-beta/rev/5bd868ce2fd08433b06a727c679ab7fd3918274d
Can the task configuration be modified with the current syntax to always use 3h on non-trunk branches?
Comment 39•6 years ago
|
||
(In reply to Sebastian Hengst [:aryx] (needinfo on intermittent or backout) from comment #38)
We did that increase for beta 68 yesterday: https://hg.mozilla.org/releases/mozilla-beta/rev/5bd868ce2fd08433b06a727c679ab7fd3918274d
Can the task configuration be modified with the current syntax to always use 3h on non-trunk branches?
There may be a way to achieve this with a transform in the taskgraph code, but I think once we move to shippable builds on this branch this problem may go away.
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
Comment 46•6 years ago
|
||
Comment 47•6 years ago
|
||
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
Updated•5 years ago
|
Description
•