Can only run one soyuz uploader at a time
Bug #29694 reported by
Christian Reis
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
High
|
Unassigned | ||
Bug Description
Multiple instances of the Soyuz uploader should be able to run simultaneously; they are currently serialized by a big lock in process-upload.py
| Changed in launchpad: | |
| status: | Unconfirmed → Confirmed |
| Changed in launchpad: | |
| assignee: | nobody → launchpad-infrastructure |
| affects: | launchpad-foundations → soyuz |
Revision history for this message
| Julian Edwards (julian-edwards) wrote Re: the Soyuz uploader should use finer resolution locking | #1 |
| tags: | added: ppa soyuz-upload |
| Changed in launchpad: | |
| importance: | Medium → High |
| tags: | added: nodowntime |
| summary: |
- the Soyuz uploader should use finer resolution locking + Can only run one soyuz uploader at a time |
| description: | updated |
To post a comment you must log in.
Rob, this seems pertinent to what we were talking about recently.
We also need to fix this so that people can't copy the same package twice before the first transaction gets committed.