Launchpad itself

Vivid + AMD64 Builds Randomly Fail

Asked by fidian

I am experiencing problems building packages in my PPA. I've done a trivial change to the rules file in order to install the binary in a new directory and the build failed. When the build fails I am unable to get a buildlog so this appears to be a problem that I can't diagnose.

Perhaps there's an issue with the vivid build machines?

Retrying the package repeatedly appears to make it work because the bash-2.00.0 package had failed twice and now is built successfully but not yet published at this time.

My PPA: https://launchpad.net/~team-mayhem/+archive/ubuntu/multishell/+packages
Screen shot of a failed build: http://public.rumkin.com/ppa-vivid-amd64.png (will remove after some time)

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
fidian (fidian) said : 		#1

The package in my example was published successfully.

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

Thanks for reporting this. There was a temporary problem about 15 hours ago that caused some random subset of builds to think that the vivid amd64 chroot didn't exist. We've cleared this and it should work again now.

Revision history for this message
fidian (fidian) said : 		#3

Awesome, thanks. How would I have known about this outage? I didn't see anything on the system status page and no other bugs were reported. I'd rather not pester people with known issues.

If this should be raised as a separate bug, please let me know.

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

We didn't know about it until looking into the question you filed, unfortunately! It was sufficiently intermittent that it managed to evade our normal checks.

Revision history for this message
fidian (fidian) said : 		#5

Thanks for the very fast replies!

Revision history for this message
fidian (fidian) said : 		#6

Thanks Colin Watson, that solved my question.