Confirmed users
571
edits
Sheriffing/How To/Intermittent bugs: Difference between revisions
Jump to navigation
Jump to search
Sheriffing/How To/Intermittent bugs (view source)
Revision as of 17:06, 7 November 2019
, 7 November 2019→Machine-specific failures: terminating workers from the command line if worker is from new provisioner
(Added accessing taskcluster logs for exceptions) |
(→Machine-specific failures: terminating workers from the command line if worker is from new provisioner) |
||
| Line 111: | Line 111: | ||
Terminate the machine if you discover such an issue: | Terminate the machine if you discover such an issue: | ||
See steps below if there is no '''Terminate''' button. | |||
# In Treeherder with the job selected, click the link '''Task: <something>''' at the bottom left. | # In Treeherder with the job selected, click the link '''Task: <something>''' at the bottom left. | ||
| Line 119: | Line 121: | ||
* If in doubt, terminate it. | * If in doubt, terminate it. | ||
* If you quarantine a machine, let #ci on IRC know. | * If you quarantine a machine, let #ci on IRC know. | ||
The new worker provisioner doesn't support terminating machines from the browser yet - the '''Terminate''' button is missing on the Taskcluster page and the provisioner name doesn't mention '''hardware''' (like in 'releng-hardware'). These machines have to be removed from the command line: | |||
Initial setup: | |||
# Download the [https://github.com/taskcluster/taskcluster/releases/ latest taskcluster executable] (taskcluster-linux-amd64). | |||
# Run <code>which taskcluster</code> in your console terminal. | |||
# Replace the file from the <code>which</code> command with the download one. | |||
# In the file manager, right click the <code>taskcluster</code> file > 'Properties' > 'Permissions' and set 'Allow executing file as program' if it is not enabled yet. | |||
# In the console, run <code>taskcluster</code> to confirm the application gets found. | |||
Terminating the machine from the command line: | |||
Before the taskcluster migration on November 9th 2019: | |||
* Run <code>export TASKCLUSTER_ROOT_URL=https://taskcluster.net</code><br> | |||
If the migration already took place, run this instead:<br> | |||
* Run <code>export TASKCLUSTER_ROOT_URL=https://firefox-ci-tc.services.mozilla.com</code> | |||
* Sign in: <code>eval `taskcluster signin --scope worker-manager:*`</code> | |||
* Log in in the browser, close the browser after you clicked 'Create Client'. | |||
* The syntax for terminating a worker is <code>taskcluster api workerManager removeWorker <workerPoolId> <workerGroup> <workerId></code><br/> | |||
Example: | |||
The page for the worker lists: <code>gecko-3 / worker-types / b-linux / aws / i-07985396a2efa2ed1</code> as identifier<br/> | |||
The command to run is: | |||
<code>taskcluster api workerManager removeWorker gecko-3/b-linux aws i-07985396a2efa2ed1</code> | |||
== How to file a security bug == | == How to file a security bug == | ||