685348 - Reboot after all jobs ?

Status: RESOLVED WONTFIX

(Infrastructure & Operations Graveyard :: CIDuty, task, P3)

Description

[Nick Thomas [:nthomas] (UTC+12)]

Jobs like l10n dep/nightlies and those based on ScriptFactory (like SpiderMonkey, Valgrind, NanoJIT, fuzzing) don't reboot after the job completes. This makes it hard for idleizer + nagios to work together, because you can have slaves doing jobs but reporting to buildbot-start in between.

Comment 1

[Nick Thomas [:nthomas] (UTC+12)]

(In reply to Nick Thomas [:nthomas] from comment #0)
> Jobs like l10n dep/nightlies and those based on ScriptFactory (like
> SpiderMonkey, Valgrind, NanoJIT, fuzzing) don't reboot after the job
> completes. This makes it hard for idleizer + nagios to work together,
> because you can have slaves doing jobs but reporting to buildbot-start in
> between.

*cough* ... not reporting to buildbot-start in between.

Comment 2

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

Found in triage. Not sure if this depends on, or should be DUP'd with, bug#660080.

Comment 3

[Nick Thomas [:nthomas] (UTC+12)]

Desktop l10n reboot these days, as do the newer mozharness jobs, but ScriptFactory still do not. AFAIK all test slaves reboot or are verified after each job.

I'm not sure that this bug is still relevant today - we have idleizer on in many places and have given up monitoring buildbot start. Also might be going in a different direction with slave api. coop, what say you ?

Comment 4

[Chris AtLee [:catlee]]

Not going to do this in favour of bug 1028191, 660080