Closed
Bug 1045194
Opened 10 years ago
Closed 9 years ago
spider hazard builds do not reboot after they finish
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jlund, Assigned: sfink)
Details
Attachments
(1 file)
4.04 KB,
patch
|
jlund
:
review+
|
Details | Diff | Splinter Review |
for b2g, desktop, l10n, and spider mozharness builds, we avail of {Script,Signing}Factory to create the buildbot job. Normally we pass a reboot_cmd to that Factory so it will call reboot() as the last step. spider builds do not do this. Assuming these builds are not special and we actually want to reboot post build, we will need to add reboot_cmd into mozilla/config.py in the respective platform dicts.
Assignee | ||
Comment 1•9 years ago
|
||
afaict, this is all that's needed. (And it's what you helpfully described in comment 0.)
Attachment #8542215 -
Flags: review?(jlund)
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → sphink
Status: NEW → ASSIGNED
Reporter | ||
Comment 2•9 years ago
|
||
Comment on attachment 8542215 [details] [diff] [review] Hazard builds need to reboot Review of attachment 8542215 [details] [diff] [review]: ----------------------------------------------------------------- ship it! :)
Attachment #8542215 -
Flags: review?(jlund) → review+
Assignee | ||
Comment 3•9 years ago
|
||
Darn it, forgot to record the r=jlund in the commit. I suppose it's not critical. https://hg.mozilla.org/build/buildbot-configs/rev/95205c5c1956
Comment 4•9 years ago
|
||
In production: https://hg.mozilla.org/build/buildbot-configs/rev/95205c5c1956
Assignee | ||
Updated•9 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•