Closed MartinNowak closed 10 years ago
'll take a closer look at this tonight as it does look like a reasonable set of changes.
However, this change doesn't address the largest source of pull failures.. git / github interaction hanging. I've been planning on implementing a timeout / retry mechanism at the driver.sh level around all tasks that would solve the problem in general (hung github interaction, hung compilation, hung tests, etc). I
I hacked something together that should do the job. It seems like driver.sh is the right place to integrate it, but you probably know better what cleanup to perform etc. https://gist.github.com/dawgfoto/6080730
Have you gotten to the pull yet?
Seems like the Win64 machine hangs currently (test), so it would be great to automate this.
I haven't forgotten about this. The win64 problem is much different. The host doesn't exist any more.
Merged by hand due to recently introduced conflicts. Thanks for the changes.
see commit eed04206da1a8256d828d953f315f96e51860721
There is also this script to watchdog and kill hanging testers. I won't get to this any time soon, but maybe you know a useful place for it.
Yeah.. I've had that link bookmarked for when I have time to play with it. I highly suspect I'm going to have to get a little platform specific about it, particularly on the windows side.
I highly suspect I'm going to have to get a little platform specific about it, particularly on the windows side.
Haven't tried Windows and it might likely not work und cygwin or whatever the autotester runs on.
For a github 503 error, see here.