Closed
Bug 1441820
Opened 6 years ago
Closed 6 years ago
Quarantine on GECKO-T-W10-64-HW instances
Categories
(Infrastructure & Operations :: RelOps: General, task)
Infrastructure & Operations
RelOps: General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: zfay, Assigned: markco)
References
Details
I have quarantined a number of instances from gecko-t-win10-64-hw. These instances had the last 10+ tasks resolved as exception (orange). Can relops take a look at them? These instances are: T-W1064-MS-117 T-W1064-MS-119 T-W1064-MS-121 T-W1064-MS-127 T-W1064-MS-152 T-W1064-MS-163 T-W1064-MS-167 T-W1064-MS-197 T-W1064-MS-207 T-W1064-MS-208 T-W1064-MS-218 T-W1064-MS-258 T-W1064-MS-269 Thanks in advance!
Comment 1•6 years ago
|
||
I also quarantined some today. The full list of releng-hardware/gecko-t-win10-64-hw quarantined workers is currently: T-W1064-MS-034 T-W1064-MS-037 T-W1064-MS-075 T-W1064-MS-112 T-W1064-MS-117 T-W1064-MS-119 T-W1064-MS-121 T-W1064-MS-127 T-W1064-MS-129 T-W1064-MS-152 T-W1064-MS-167 T-W1064-MS-197 T-W1064-MS-200 T-W1064-MS-207 T-W1064-MS-208 T-W1064-MS-218 T-W1064-MS-258 T-W1064-MS-269 This list can be refreshed by visiting https://tools.taskcluster.net/provisioners/releng-hardware/worker-types/gecko-t-win10-64-hw and choosing the filter "quarantined".
Comment 2•6 years ago
|
||
I also quarantined some of them (add them to the list from comment 1): T-W1064-MS-078 T-W1064-MS-198 T-W1064-MS-221
Comment 3•6 years ago
|
||
First day of spring, so lets add the following quarantined instances to the list: T-W1064-MS-113 T-W1064-MS-123 T-W1064-MS-153 T-W1064-MS-158 T-W1064-MS-164 T-W1064-MS-084 T-W1064-MS-169 T-W1064-MS-215
Comment 4•6 years ago
|
||
The last 10+ resolved tasks by these machines was marked as exceptions so I quarantined them. T-W1064-MS-065 T-W1064-MS-072 T-W1064-MS-082 T-W1064-MS-086 T-W1064-MS-088 T-W1064-MS-111 T-W1064-MS-156 T-W1064-MS-174 T-W1064-MS-214 T-W1064-MS-248 T-W1064-MS-256 T-W1064-MS-257
Reporter | ||
Comment 5•6 years ago
|
||
Added these machines to the quarantine list since they have the entire first page of tasks solved as exception. 5th March 2018: T-W1064-MS-207 T-W1064-MS-221 T-W1064-MS-258
Comment 6•6 years ago
|
||
Adding the following: T-W1064-MS-078 T-W1064-MS-129 T-W1064-MS-153 T-W1064-MS-219
Comment 7•6 years ago
|
||
Mark's been working on the moonshots to fix a bunch of the issues that came up last week (when this was originally filed), and has been re-installing them. Once that's finished, these will need to be unquarantined to pick up jobs; but we should also make sure that there aren't any other lingering issues.
Assignee: relops → mcornmesser
Flags: needinfo?(mcornmesser)
Assignee | ||
Comment 8•6 years ago
|
||
Is there documentation on how to quarantine and unquarantine workers? I would like to quarantine several more while I am testing, and then after I am done testing I can go through an unquarantine all.
Flags: needinfo?(mcornmesser)
Reporter | ||
Comment 9•6 years ago
|
||
(In reply to Mark Cornmesser [:markco] from comment #8) > Is there documentation on how to quarantine and unquarantine workers? I > would like to quarantine several more while I am testing, and then after I > am done testing I can go through an unquarantine all. Hey Mark, we recently created a page about this. Hope it helps. Feel free to contact me as well if you stumble across anything else build duty related. https://wiki.mozilla.org/BuildDuty:QuarantineInstances
Assignee | ||
Comment 10•6 years ago
|
||
I believe all these are now pickup tasks.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•