build processed with uploadprocessor while it is still set to BUILDING
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
Jelmer Vernooij | ||
Bug Description
Some builds appear to be processed by the upload processor before their status is set to UPLOADING (still set to "BUILDING"). We've hit this particular issue more than once with the i386 build for a particular version of openjdk-6. It hasn't happened for the other architectures for some reason.
This suggests there is a race condition involved where, in the buildd manager, we add a build to the uploader queue before the build status is set to UPLOADING. However, we explicitly flush the database store so there is no race condition between the buildd manager and the archive uploader (lib/lp/
When the upload processor processes a build that has a status other than UPLOADING it moves the build to failed.
2010-11-26 06:29:11 WARNING Expected build status to be 'UPLOADING', was BUILDING. Moving to failed.
Related branches
- Jeroen T. Vermeulen (community): Approve (code)
-
Diff: 39 lines (+5/-6)2 files modifiedlib/lp/buildmaster/model/builder.py (+0/-1)
lib/lp/buildmaster/model/packagebuild.py (+5/-5)
| Changed in soyuz: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| assignee: | nobody → Jelmer Vernooij (jelmer) |
| description: | updated |
| Changed in soyuz: | |
| status: | Triaged → In Progress |
| Launchpad QA Bot (lpqabot) wrote Bug fixed by a commit | #1 |
| tags: | added: qa-needstesting |
| Changed in soyuz: | |
| status: | In Progress → Fix Committed |
| tags: |
added: qa-ok removed: qa-needstesting |
| Changed in soyuz: | |
| status: | Fix Committed → Fix Released |
| Changed in launchpad: | |
| milestone: | none → 11.01 |
Fixed in stable r12024 <http://