Closed
Bug 1387429
Opened 7 years ago
Closed 7 years ago
docker-worker: Superseding is broken if primary task aborts
Categories
(Taskcluster :: Workers, defect)
Taskcluster
Workers
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: pmoore, Unassigned)
References
Details
In short, see https://github.com/petemoore/test-supersede/ This will create a set of 5 tasks, where one supercedes all the others. The superceding task intentionally fails (max run time exceeded). All of the tasks that should be superseded by it are then run individually (with no superseding) since superseding only works for task run 0 (which has been "used up" with a fake "worker-shutdown" exception in the abort of the primary task). The test-supersede repo above demonstrates the problem.
Comment 1•7 years ago
|
||
That's intentional: we don't want to try to repeatedly supersede a task, so we only supersede run 0. Re-runs are fairly rare, so this is a nice way of "failing open"
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
Assignee | ||
Updated•5 years ago
|
Component: Docker-Worker → Workers
You need to log in
before you can comment on or make changes to this bug.
Description
•