When we reach the end of certain code paths in kittenherder, we *know* that the next step is filing a bug to recover the slave, e.g. a talos-r3 machine is unpingable. There's no sense in waiting for a human to notice that. kittenherder (or replacement) should file that bug (and do the associated dance with the appropriate reboots bug) automatically. catlee already has some code to do this: https://github.com/catlee/relengbot/blob/master/relengbot/slave_bugger.py
For some reason this bug is marked as a goal. "[ON TRACK] better slave issue tracking bug 859403"
(In reply to Armen Zambrano G. [:armenzg] (Release Enginerring) from comment #1) > For some reason this bug is marked as a goal. > "[ON TRACK] better slave issue tracking bug 859403" It's marked as a goal because it's pretty important, and we all agreed to it at the start of the quarter.
Product: mozilla.org → Release Engineering
slaveapi does this now.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Whiteboard: [automation][capacity] → [automation][capacity][slaveapi]
Component: Tools → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.