On Fri, Apr 17, 2015 at 8:57 AM, Axel Beckert <a...@debian.org> wrote: > jenk...@jenkins.debian.net wrote: >> See <https://jenkins.debian.net/job/lintian-tests_wheezy/135/changes> > Hrm, I don't see why this should have failed. > >> Running legacy-debug 1.0... building... testing... ok. >> make: *** [runtests] Terminated >> Fri Apr 17 05:14:40 UTC 2015 - /srv/jenkins/bin/chroot-run.sh stopped >> running as /tmp/jenkins-script-iGyJSuX9, which will now be removed. >> Build step 'Execute shell' marked build as failure > > I found no other failure visible in > https://jenkins.debian.net/job/lintian-tests_wheezy/135/console so I > assume some time limit has been reached and that this is no real > issues with my commits.
the limit reached is a 6 hours timeout. As you can see here https://jenkins.debian.net/job/lintian-tests_wheezy/buildTimeTrend it reached and passed it, then jenkins killed the job. Also the current run is probably going to hit the timeout, and it's already stuck at the very same step of the last timeout. I don't really know how do you run during the tests, but one case of such failure is due to some program waiting for input (just wild-guessing) -- regards, Mattia Rizzolo GPG Key: 4096R/B9444540 http://goo.gl/I8TMB more about me: http://mapreri.org Launchpad User: https://launchpad.net/~mapreri Ubuntu Wiki page: https://wiki.ubuntu.com/MattiaRizzolo -- To UNSUBSCRIBE, email to debian-lint-maint-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAHKYmeuuEDcf_LYPrBR+4=33euq3pczv2cf6t8q3gfohjmc...@mail.gmail.com