improve handling of timeouts

[thesurlydev]

It looks as though better handling of timeouts is needed. For example, this build has exceeded 5 minutes but there was no indication of the timeout getting exceeded:

https://lambci-buildresults-s0ynpdlndv0i.s3.amazonaws.com/gh/digitalsanctum/guava/builds/2/e3fb54dccc4353763d6ba981b59e6dd8.html

[mhart]

Yeah, that's been on my mind for a while 👍 It's a good point.

Problem is it's not actually possible to determine whether the Lambda timeout was exceeded or not because the process just exits. But we could certainly add some sort of warning – or even just fail with a few seconds to spare so at least you can see it in the build.

[faceleg]

+1 to purposely failing before timeout

[Jonnx]

+1

[madmod]

+1 iojs.org is down right now which is causing a new build to start over every 5 minutes. I suspect many others using lambci are also having this problem right now.