Stuck build machines

Asked by Brian Rogers

I went over the builds and found that the following build machines appear to be stuck and in need of a reset:

https://launchpad.net/builders/bohrium building https://launchpad.net/~mmaruska/+archive/mmc-pipeline/+build/1945426

https://launchpad.net/builders/charichuelo building https://launchpad.net/~kernel-ppa/+archive/pre-proposed/+build/1953920

https://launchpad.net/builders/promethium building https://launchpad.net/~pali/+archive/pali/+build/1950957

https://launchpad.net/builders/titanium building https://launchpad.net/builders/titanium

https://launchpad.net/builders/terranova building https://launchpad.net/~chromium-daily/+archive/ppa/+build/1952454

charichuelo and titanium are saying "No space left on device"
promethium's buildlog has a partial line printed at the end
bohrium is cleaning up after a build attempt, but not progressing

terranova crashed again the same way it crashed on my own kernel build in question 124176:

Session terminated, killing shell...make[1]: *** [out/Release/obj.target/chrome/chrome/app/chrome_dll_main.o] Terminated
make: *** wait: No child processes. Stop.
make: *** Waiting for unfinished jobs....
make: *** wait: No child processes. Stop.
 ...killed.

Could terranova be having a hardware stability problem?

Also, one machine seems to be in a loop:

https://launchpad.net/builders/mercury building https://launchpad.net/~wesleys/+archive/ppa/+build/1952793 over and over

The build status screen doesn't make sense:

 Currently building on mercury (virtual) on mercury (virtual)

    * Started 5 minutes ago
    * Finished 12 minutes ago (took 23 hours, 52 minutes, 24.9 seconds)

(Yes, it says 'building on mercury (virtual)' twice and indicates that it finished before it started!)

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Brian Rogers
Solved:
Last query:
Last reply:
Revision history for this message
Brian Rogers (brian-rogers) said :
#1

These systems appear to have been reset.

Revision history for this message
Julian Edwards (julian-edwards) said :
#2

Ah yes we fixed it but I forgot to reply to your question!