develooper Front page | perl.perl5.porters | Postings from January 2017

the trouble with win32 jenkins (Re: Build failed in Jenkins:perl5-win32 #3301)

Thread Next
From:
Craig A. Berry
Date:
January 26, 2017 20:26
Subject:
the trouble with win32 jenkins (Re: Build failed in Jenkins:perl5-win32 #3301)
Message ID:
CA+vYcVzQcupNvmc-w0bgNjR1o1+s-1WATxYkEMa-t899nYE-JQ@mail.gmail.com
On Thu, Jan 26, 2017 at 11:11 AM, Abigail <abigail@abigail.be> wrote:
> On Thu, Jan 26, 2017 at 05:08:47PM +0100, jenkins@perl.space wrote:
>>
>> Build timed out (after 90 minutes). Marking the build as failed.
>
>
> This seems to happen quite frequently. Should the time out be increased,
> or is something really wrong for the binary produced on Windows?

It looks like the timeout was recently increased from 60 minutes to 90
minutes to no avail, which might mean it's really hung and no amount
of waiting will help.

As I asked a week ago at:
<http://www.nntp.perl.org/group/perl.perl5.porters/2017/01/msg242369.html>

>>
Does anybody have the ability to run a win32 smoker?  Does anyone know
what's causing the win32 jenkins runs to hang and/or have any ideas
about how to fix them?
>>

That was Warnocked.  I think most everyone has learned to ignore these
reports since they are almost all false positives.  Which means they
aren't really providing much value but they are contributing
significantly to the volume of the mailing list, which runs on
volunteer time and (I believe) volunteer hardware.

Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About