Re: Build failed in Jenkins: lintian-tests_wheezy #135

[Niels Thykier <niels@thykier.net>]

On 2015-04-17 08:57, Axel Beckert wrote:
> Hi,
> 
> jenkins@jenkins.debian.net wrote:
>> See <https://jenkins.debian.net/job/lintian-tests_wheezy/135/changes>
>>
>> [...]
> 
>> 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.
> 
> 		Regards, Axel
> 

Hi Axel,

Indeed, that is probably the most likely explanation and sadly we got
spurious failures due to the test runner getting stuck.  My rule of
thumb is to ignore the result if there is no summary or an "obvious"
breakage in the part of the quoted log.

I suspect is because we are still using "threads".  I got a branch
somewhere moving to IO::Async that might resolve this.  I have been
stalling it a bit to avoid deliberately breaking support the previous
Ubuntu LTS (Precise, I think), which does not support a new enough
IO::Async.
  Though, I think it might be time to apply it once Stretch opens.

Thanks,
~Niels