Status

Release Engineering
Platform Support
P3
normal
RESOLVED WONTFIX
7 years ago
4 years ago

People

(Reporter: nthomas, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [buildbot][idleizer])

(Reporter)

Description

7 years ago
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.
(Reporter)

Comment 1

7 years ago
(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.

Updated

7 years ago
Priority: -- → P3
Hardware: x86 → All
Whiteboard: [buildbot][idleizer]
(Assignee)

Updated

5 years ago
Product: mozilla.org → Release Engineering
Found in triage. Not sure if this depends on, or should be DUP'd with, bug#660080.
Component: Other → Platform Support
Depends on: 660080
(Reporter)

Comment 3

5 years ago
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 ?
Not going to do this in favour of bug 1028191, 660080
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.