Open
Bug 1533697
Opened 7 years ago
Updated 3 years ago
generic-worker: abort worker and publish logs if task user has already been used
Categories
(Taskcluster :: Workers, enhancement)
Taskcluster
Workers
Tracking
(Not tracked)
REOPENED
People
(Reporter: pmoore, Unassigned, Mentored)
References
Details
(Keywords: good-first-bug, Whiteboard: [lang=go])
From bug 1531878 comment 19:
Check that no task log file exists for the current task user when the worker starts up. If it does, the worker should exit with the existing exit code 69 "Worker panic":
69 Worker panic - either a worker bug, or the environment is not suitable for running
a task, e.g. a file cannot be written to the file system, or something else did
not work that was required in order to execute a task. See config setting
shutdownMachineOnInternalError.
Since it should not be possible for a task user already to have been used (due to bug 1533694), the worker should abort, rather than gracefully handling the situation, since it indicates that something is seriously wrong and that the environment is non-deterministic.
| Reporter | ||
Updated•6 years ago
|
Mentor: pmoore
Keywords: good-first-bug
| Reporter | ||
Updated•6 years ago
|
Whiteboard: [lang=go]
| Reporter | ||
Updated•6 years ago
|
QA Whiteboard: [lang=go]
| Reporter | ||
Comment 1•5 years ago
|
||
Not actively working on this at the moment.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INACTIVE
| Reporter | ||
Comment 2•3 years ago
|
||
Reopening inactive bugs, because they may still need attention. Historically, inactive bugs were closed, but this hides the fact there are genuine issues which have not been resolved.
| Reporter | ||
Updated•3 years ago
|
Status: RESOLVED → REOPENED
Resolution: INACTIVE → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•