Launchpad itself

Problems with automatic import of svn branches

Asked by Luis Felipe Strano Moraes

I'm having problems with the automatic import of a few subversion branches related to the svn project. The branches are failing to import after running for hours. I believe it is the same issue as https://bugs.launchpad.net/bugs/343207 (also commented there, thanks for Matsubara for pointing that bug out).
The branches I want to import are:
 * http://llvm.org/svn/llvm-project/llvm/trunk as llvm-trunk
 * http://llvm.org/svn/llvm-project/cfe/trunk as clang-trunk
 * http://llvm.org/svn/llvm-project/llvm-gcc-4.2/trunk as llvm-gcc-4.2-trunk

I had not yet created a request for that last one, but since it's the bigger one I believe it would fail as well. The other two (with the respective failure logs) can be found here: https://code.launchpad.net/llvm

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
Michael Hudson-Doyle Edit question
Solved by:
Michael Hudson-Doyle
Solved:
Last query:
Last reply:
Whiteboard:
Assigning to mwhudson so he follows up. 20090616 danilo
Revision history for this message
Luis Felipe Strano Moraes (luis-strano) said : 		#1

Might have missed the actual question, which was: can those branches be imported manually or something like that?

Revision history for this message
Michael Hudson-Doyle (mwhudson) said : 		#2

Well so far, the imports have failed once, and then failed again because of the rollout, and both have been running since then -- it's possible they will actually succeed this time. Let's wait and see before doing the manual thing?

Revision history for this message
Luis Felipe Strano Moraes (luis-strano) said : 		#3

Well, the llvm-gcc-4.2 import is having a lot of network issues, one of the imports was running for 46 hours before having problems. The llvm one completed, but it had a different issue (already sent another question about it), and clang imported succesfully. If the llvm-gcc-4.2 one keeps getting failures, could it be done manually ?

Revision history for this message
Michael Hudson-Doyle (mwhudson) said : 		#4

I'm downloading the repo via svnsync now and will try a local from import when that's done. It will take a while, I guess!

Revision history for this message
Michael Hudson-Doyle (mwhudson) said : 		#5

Just a quick update to say that I haven't forgotten this, but each step of the process takes a long time with a repository like this.

The manual import is running now though.

Revision history for this message
Best Michael Hudson-Doyle (mwhudson) said : 		#6

The imports are all now working, as far as I can see.

Revision history for this message
Luis Felipe Strano Moraes (luis-strano) said : 		#7

Thanks Michael Hudson, that solved my question.