[prev in list] [next in list] [prev in thread] [next in thread] 

List:       perl5-porters
Subject:    Re: the trouble with win32 jenkins (Re: Build failed in Jenkins: perl5-win32 #3301)
From:       Dennis Kaarsemaker <dennis () kaarsemaker ! net>
Date:       2017-01-27 11:25:30
Message-ID: 1485516330.3222.6.camel () kaarsemaker ! net
[Download RAW message or body]

On Thu, 2017-01-26 at 14:26 -0600, Craig A. Berry wrote:
> 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.

Yup. Runs that don't time out, finish in about 40 minutes.

> 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.

If nobody steps up to help, I'll just kill the win32 jenkins. Not only
is it timing out all the time, there are still some flaky tests that
nobody ever fixes.

-- 
Dennis Kaarsemaker
http://www.kaarsemaker.net
[prev in list] [next in list] [prev in thread] [next in thread]