Mailinglist Archive: opensuse-bugs (4766 mails)

< Previous Next >
[Bug 599186] New: ocs - commit: double up-load ? ...g
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Fri, 23 Apr 2010 10:19:46 +0000
  • Message-id: <bug-599186-21960@xxxxxxxxxxxxxxxxxxxxxxxx/>

Summary: ocs - commit: double up-load ? ...g
Classification: openSUSE
Version: unspecified
Platform: Other
OS/Version: Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: BuildService
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: mmeeks@xxxxxxxxxx
QAContact: adrian@xxxxxxxxxx
Found By: ---
Blocker: ---

When committing a large file to a remote build-service (eg. MeeGo) - it is
-incredibly- slow.

here is the flow:

rm evolution-2.30.1~20100419.tar.bz2
cp .../evolution-2.30.1~20100423.tar.bz2 .
osc addremove

osc commit
< wait for 30+ seconds - it -looks- strongly form the strace as if we are
up-loading or downloading something rather big here>
finally get the commit editor:

--This line, and those below, will be ignored--

D evolution-2.30.1~20100419.tar.bz2
A evolution-2.30.1~20100423.tar.bz2

Diff for working copy: .
Index: evolution-2.30.1~20100423.tar.bz2

Binary file evolution-2.30.1~20100423.tar.bz2 has changed

Index: evolution-2.30.1~20100419.tar.bz2

Binary file evolution-2.30.1~20100419.tar.bz2 has changed

add a banal messsage - takes about 5 seconds. Then write the log & the up-load

Deleting evolution-2.30.1~20100419.tar.bz2
Sending evolution-2.30.1~20100423.tar.bz2
Transmitting file data .
< another wait of around 30 seconds - suspicious hey ! ;->
Committed revision 5.

Can you confirm that we do not in fact do an up-load (or download) twice here ?
presumably we shouldn't have to download anything to remove a file, and we can
wait to up-load an added file until after the commit message is entered

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >