launchpad lost track of a build
Bug #676262 reported by
LaMont Jones
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Won't Fix
|
Critical
|
Unassigned | ||
launchpad-buildd |
Won't Fix
|
Critical
|
Unassigned |
Bug Description
Today about 20:30 london time, I was asked about "ross not dispatching builds". When I investigated, I found that it was, in fact, building gcc-snapshot. The last time in the build-manager log for ross was 07:30 ish this morning, which would be consistent with a reasonable start time for that build.
Once I killed the build on ross, it happily received and started buliding qt4-x11.
Clearly, some better understanding of the roots of this amnesia is in order.
tags: | added: buildd-manager |
Changed in soyuz: | |
status: | Incomplete → Triaged |
importance: | Undecided → High |
Changed in launchpad: | |
importance: | High → Medium |
importance: | Medium → Critical |
tags: | added: soyuz-build |
To post a comment you must log in.
Lamont, I've no idea what bug you're trying to report here! Can you please state:
1. Behaviour you thought was bad
2. Expected behaviour
Thanks.