Closed
Bug 878051
Opened 11 years ago
Closed 10 years ago
kittenherder should send a single, daily email report about slaves that require manual intervention
Categories
(Release Engineering :: General, defect, P2)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: coop, Assigned: coop)
References
Details
kittenherder currently sends an email at the end of every run. This email documents the actions taken: slaves rebooted, the method used, and any slaves that require manual intervention. Since the script is invoked per platform by cron every 6 hours, and history is not preserved between successive iterations, I end up with lots of kittenherder spam (it's sent only to me at present) which is not particularly useful and hence is ignored. Once we properly track slave reboot attempts from one run to the next (bug 878049), we can make this report much more useful to buildduty and send the report to release@m.c. I'd like to see a single, daily report that starts off with a list of slaves that require manual intervention. Over time as kittenherder gets better at recognizing slave states where it can file bugs automatically (bug 859403), this list should get very small. The report should also include a list of slaves for which bugs were filed over the past day. I don't think we need to report on slaves that were successfully rebooted. This report should get sent out in the early AM so buildduty can have it waiting in their inbox when they start work.
Assignee | ||
Updated•11 years ago
|
Component: Release Engineering: Machine Management → Release Engineering: Developer Tools
QA Contact: armenzg → hwine
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Assignee | ||
Comment 1•10 years ago
|
||
https://secure.pub.build.mozilla.org/builddata/reports/slave_health/buildduty_report.html
Assignee: nobody → coop
Status: NEW → RESOLVED
Closed: 10 years ago
Priority: -- → P2
Resolution: --- → WORKSFORME
Updated•7 years ago
|
Component: Tools → General
You need to log in
before you can comment on or make changes to this bug.
Description
•