linaro-release team mailing list archive

[Fathi Boudra <fathi.boudra@xxxxxxxxxx>]

** Also affects: linaro-offspring
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of linaro-
infrastructure-drivers, which is the registrant for Linaro Offspring.
https://bugs.launchpad.net/bugs/797645

Title:
  detect faulty builder and schedule to other builders in the farm as a
  fallback

Status in Linaro Offspring:
  New
Status in Offspring Image Build System:
  Confirmed

Bug description:
  All hwpacks failed to build on offspring:
  https://offspring.linaro.org/

  Looking at the 1st attempted build log on malus builder (omap3-natty):
  http://snapshots.linaro.org/build/omap3-natty/20110615/0/build-log.txt

  I: Saving copy of build setup to build results directory.
  Building for armel
  Fetching packages
  Traceback (most recent call last):
   File "/usr/bin/linaro-hwpack-create", line 66, in <module>
     builder.build()
   File "/usr/lib/pymodules/python2.6/linaro_image_tools/hwpack/builder.py",
  line 100, in build
     f.write(hwpack.manifest_text())
   File "/usr/lib/pymodules/python2.6/linaro_image_tools/hwpack/packages.py",
  line 173, in __exit__
     shutil.rmtree(tmpdir)
   File "/usr/lib/python2.6/shutil.py", line 204, in rmtree

   File "/usr/lib/python2.6/shutil.py", line 202, in rmtree

  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?

To manage notifications about this bug go to:
https://bugs.launchpad.net/linaro-offspring/+bug/797645/+subscriptions