Launchpad itself

Rare and Awkward Failure from Launchpad to Build arch am64 in 33 sec. No Log

Asked by Pascal Mons

Yesterday I did successfully build package gimplensfun in my PPA ppa:anton+/photo-video-apps for Trusty and Vivid in arch amd64 and i386, However in Wily I get only the i386 arch build. Fr the amd64 build there is no log and the build fails in 10 to 30 seconds ... Why ?

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Colin Watson
Solved:
Last query:
Last reply:
Revision history for this message
Best Colin Watson (cjwatson) said : 		#1

We've had various infrastructure failures over the end-of-year holidays which result in builds silently failing to upload and ending up in this state. Hopefully we'll get to the bottom of this once folks get back to work, but in the meantime, just retry the affected builds.

Revision history for this message
Peter Jonas (shoogle) said : 		#2

I had this problem too. Last night an amd64 build for Wily kept failing without giving a build log or any kind of error report. The same package built fine for Trusty and Vivid on i386 and amd64, and also Wily i386. I tried again this afternoon and it built fine on Wily amd64.

Revision history for this message
Pascal Mons (anton+) said : 		#3

OK Thanks. I retried a moment ago and it passed flawlessly.

Revision history for this message
Pascal Mons (anton+) said : 		#4

Thanks Colin Watson, that solved my question.

Revision history for this message
Colin Watson (cjwatson) said : 		#5

Oh, it can also happen not on uploads but because a negative response from the librarian gets incorrectly cached by a squid instance en route, and if this happens to be for the wily amd64 chroot then all wily amd64 builds after that will have a bad time. It sounds like this has been cleared, but do let us know if you happen to spot that kind of persistent failure again and we can clear it.