854064 - Jetpack jobs on the Jetpack tree need to reboot

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P2)

Description

[Phil Ringnalda (:philor)]

Despite my initial shock at realizing it, this feels like something I've known before and filed before, but I can't find any sign of it.

The jobs on the Jetpack tree just don't reboot, at all. That means we're entirely dependent on them successfully running to completion, and if they don't and the next job the slave catches on another tree is Talos, which objects to being expected to run on a machine that already has Firefox running on it, you get https://tbpl.mozilla.org/php/getParsedLog.php?id=20996472&tree=Mozilla-Inbound https://tbpl.mozilla.org/php/getParsedLog.php?id=20996591&tree=Mozilla-Inbound https://tbpl.mozilla.org/php/getParsedLog.php?id=20996339&tree=Mozilla-Inbound red.

If the next job isn't Talos, but instead is a suite that doesn't check for another Firefox still running and doing who knows what, what you get is... we have absolutely no idea. N jobs on m trees doing... anything, or nothing, absolutely nobody knows what and the cause isn't going to be detected.

Comment 1

[Armen [:armenzg]]

Attachment: reboot jetpack jobs

Comment 2

[Armen [:armenzg]]

Comment on attachment 730177 [details] [diff] [review]
reboot jetpack jobs

http://hg.mozilla.org/build/buildbotcustom/rev/31ad2fea8289

Comment 3

[Armen [:armenzg]]

https://tbpl.mozilla.org/php/getParsedLog.php?id=21340404&tree=Jetpack&full=1

========= Started reboot slave lost (results: 0, elapsed: 0 secs) (at 2013-04-02 01:31:54.709997) =========

========= Finished reboot slave lost (results: 0, elapsed: 0 secs) (at 2013-04-02 01:31:55.609161) =========