Build killed with signal 15 after 150 minutes of inactivity

Asked by Oibaf

I am trying to backport llvm-3.2 on my PPA ( https://launchpad.net/~oibaf/+archive/graphics-drivers/+packages ). precise (32 and 64 bit) built OK, as well as 64 bit quantal. 32 bit quantal however failed due to a timeout:

-- Testing: 6841 tests, 1 threads --

Session terminated, terminating shell... ...terminated.
Testing: 0 .. 10.. 20.. 30.. 40.. 50.. 60make[3]: *** wait: No child processes. Stop.
make[3]: *** Waiting for unfinished jobs....
make[3]: *** wait: No child processes. Stop.
make[2]: *** wait: No child processes. Stop.
make[2]: *** Waiting for unfinished jobs....
make[2]: *** wait: No child processes. Stop.
make[1]: *** wait: No child processes. Stop.
make[1]: *** Waiting for unfinished jobs....
make[1]: *** wait: No child processes. Stop.
make: *** wait: No child processes. Stop.
make: *** Waiting for unfinished jobs....
make: *** wait: No child processes. Stop.
Build killed with signal 15 after 150 minutes of inactivity

The build log is here:
https://launchpadlibrarian.net/126102736/buildlog_ubuntu-quantal-i386.llvm-3.2_3.2%7Erc3-1%7Eexp1ubuntu1%7Eq%7Egd_FAILEDTOBUILD.txt.gz

I build it again but with the same results. Probably the machine building this is too slow and leads to the timeout. Can the build timeout of my PPA be augmented to avoid this problem?

Thanks.

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Oibaf
Solved:
Last query:
Last reply:
Revision history for this message
William Grant (wgrant) said :
#1

We can't increase the timeout. If the test suite really does take more than 2.5 hours, you'll need to increase the verbosity of the output so the builder can see that something is still happening.

Revision history for this message
Oibaf (oibaf) said :
#2

Thanks, this was due to a real problem in the llvm test suite, hanging forever with gcc 4.7 on x86: http://llvm.org/bugs/show_bug.cgi?id=14534