Closed
Bug 558873
Opened 15 years ago
Closed 13 years ago
Auto-reboot SeaMonkey (tests) boxes
Categories
(SeaMonkey :: Release Engineering, enhancement)
SeaMonkey
Release Engineering
Tracking
(Not tracked)
RESOLVED
FIXED
Future
People
(Reporter: sgautherie, Unassigned)
Details
I don't know how this works exactly, but rebooting has helped us in the past: not often, but sometimes.
It should also help to get rid of Windows crash dialogs (on test boxes) for example...
Am I right that triggering this should be as easy as switching to
|'builds_before_reboot': 5|
in
http://mxr.mozilla.org/build/source/buildbot-configs/seamonkey/config.py
?
Or do our boxes (still) have other issues which prevent this?
Fwiw, Firefox uses either: None, 1 or 5.
http://mxr.mozilla.org/build/search?string=builds_before_reboot&case=on
Flags: in-testsuite-
Comment 1•15 years ago
|
||
1) I have no idea what benefit it would have in our current setup (with puppet/OPSI/etc. it makes sense because things can be executed on startup)
2) We know that Windows boxes probably fail if we don't manually log in, which is out of the question with this setup
3) Any manual interaction (remote admin) with the boxes is futile if they might reboot automatically while you're logged in, so things like manually clobbering can't be done with this setup
4) It slows down boxes as reboot take some time, up to a few minutes per box
Severity: normal → enhancement
Target Milestone: --- → Future
Comment 2•13 years ago
|
||
I believe this bug has been fixed. Currently the build slaves reboot upon
completion of the job (irregardless if the tests/builds failed,
were good or had an exception).
Fixed by http://hg.mozilla.org/build/buildbot-configs/rev/a3bb108c6746.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•