Missing chroots should always fail the job, not the builders

Bug #681811 reported by Julian Edwards
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

For example:

2010-11-26 14:55:33+0000 [QueryProtocol,client] startBuild(http://rubidium.buildd:8221/, linux-firmware, 1.38, Release)
2010-11-26 14:55:33+0000 [QueryProtocol,client] Scanning rubidium failed with: Missing CHROOT for deribuntu4/demented/i386
2010-11-26 14:55:33+0000 [QueryProtocol,client] builder rubidium failure count: 3, job 'i386 build of linux-firmware 1.38 in deribuntu4 demented RELEASE' failure count: 2

This will eventually fail the builder. The code should detect a missing chroot and fail the build.

Changed in soyuz:
status: New → Triaged
importance: Undecided → Medium
tags: added: buildd-manager
Changed in launchpad:
importance: Medium → High
Revision history for this message
Robert Collins (lifeless) wrote :

This is fixable when it happens, though its annoying (obviously).I think for now its less important than most of the other soyuz bugs.

Changed in launchpad:
importance: High → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.