2006-01-25 20:54:50 |
Christian Reis |
bug |
|
|
added bug |
2006-01-31 11:51:56 |
Dafydd Harries |
title |
Multiple instances of uploader should run simultaneously |
the Soyuz uploader should use finer resolution locking |
|
2006-01-31 11:52:08 |
Dafydd Harries |
launchpad: status |
Unconfirmed |
Confirmed |
|
2006-01-31 11:52:08 |
Dafydd Harries |
launchpad: statusexplanation |
|
|
|
2006-01-31 17:10:20 |
Dafydd Harries |
launchpad: assignee |
|
launchpad-infrastructure |
|
2010-11-13 06:10:25 |
Curtis Hovey |
affects |
launchpad-foundations |
soyuz |
|
2010-11-15 09:11:33 |
Julian Edwards |
bug |
|
|
added subscriber Robert Collins |
2010-11-15 09:12:41 |
Julian Edwards |
tags |
infrastructure |
infrastructure ppa soyuz-upload |
|
2011-05-30 08:09:17 |
William Grant |
removed subscriber Canonical Launchpad Engineering |
|
|
|
2011-09-20 20:46:23 |
Robert Collins |
launchpad: importance |
Medium |
High |
|
2011-09-20 20:46:46 |
Robert Collins |
tags |
infrastructure lp-soyuz ppa soyuz-upload |
infrastructure lp-soyuz nodowntime ppa soyuz-upload |
|
2011-09-20 20:47:17 |
Robert Collins |
summary |
the Soyuz uploader should use finer resolution locking |
Can only run one soyuz uploader at a time |
|
2011-09-20 20:47:38 |
Robert Collins |
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 There's a large comment by Niemeyer that Daniel needs to look through and consider carefully. |
Multiple instances of the Soyuz uploader should be able to run simultaneously; they are currently serialized by a big lock in process-upload.py |
|