Closed
Bug 1496196
Opened 6 years ago
Closed 5 years ago
[tracking] make hardware workers not expire
Categories
(Taskcluster :: UI, enhancement)
Taskcluster
UI
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1562975
People
(Reporter: zfay, Assigned: bstack)
Details
Filing this bug to track one of the action items discussed in the relops/taskcluster/ciduty meeting.
A very important improvement that was discussed was making HW workers not expire from the worker explorer (have 1000 year expiration time, similar to how quarantine works). At the moment this is set to 24h after which the worker disappears from the worker-explorer.
Why change it?
As demonstrated in the meeting, ciduty are using a script to check for missing HW workers. All teams agreed that implementing this change would be an improvement, and thus we would rely on the data of when the last task was completed to find and troubleshoot problematic workers.
Assignee | ||
Comment 1•6 years ago
|
||
It looks like we can quite easily just redeclare the hardware workertypes to have 1000 year expirations. Will look into to doing that today.
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → bstack
Status: NEW → ASSIGNED
Updated•6 years ago
|
Component: Tools → UI and Tools
Assignee | ||
Comment 2•5 years ago
|
||
Marking this as a dupe. Not because the new bug is the same as this one but because it will fix this when done.
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•