detect faulty builder and schedule to other builders in the farm as a fallback
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linaro Offspring |
New
|
Undecided
|
Unassigned | ||
Offspring |
Fix Released
|
Medium
|
Nicola Heald |
Bug Description
All hwpacks failed to build on offspring: https:/
Looking at the 1st attempted build log on malus builder (omap3-natty):
http://
I: Saving copy of build setup to build results directory.
Building for armel
Fetching packages
Traceback (most recent call last):
File "/usr/bin/
builder.build()
File "/usr/lib/
line 100, in build
f.write(
File "/usr/lib/
line 173, in __exit__
shutil.
File "/usr/lib/
File "/usr/lib/
OSError: [Errno 5] Input/output error: '/tmp/tmp7dymq0'
E: A fatal error has ocurred. Shutting down.
After that, malus was wedged. I guess that the other builders were busy
to build 11.05-images, causing all the builds schedule to target malus
and the mass build ERROR.
Can we detect when a builder is stuck and schedule next build on another host?
Changed in offspring: | |
importance: | Undecided → Medium |
status: | Incomplete → Confirmed |
tags: | added: improvement scheduled |
Changed in offspring: | |
status: | Confirmed → Fix Released |
assignee: | nobody → Mike Heald (mike-powerthroughwords) |
How would you detect that malus was stuck in this case?
Thanks,
James