travis builds time out -- then keep restarting ???
hans at stare.cz
Tue Jan 2 22:28:31 UTC 2018
On Jan 02 22:20:25, raimue at macports.org wrote:
> On 01/02/2018 11:13 AM, Jan Stary wrote:
> > On Sep 15 15:37:01, ken.cunningham.webuse at gmail.com wrote:
> >> Something funny is going on with travis today.
> >> The builds keep restarting after timing out at 48 mins, I think
> >> <https://travis-ci.org/macports/macports-ports/jobs/275966013>
> > On Sep 17 06:28:57, ken.cunningham.webuse at gmail.com wrote:
> >> this is still going on. some travis builds have been running almost 6 hours, which would be great if they finally built something, but looks like it just keeps resetting and starting over...
> > On Sep 17 15:35:44, raimue at macports.org wrote:
> >> Must be an error on the side of Travis. Our configuration just runs the
> >> command and whatever causes it to restart after the timeout must be
> >> something at Travis.
> > On Sep 17 15:53:23, raimue at macports.org wrote:
> >> I do not think it is our issue if it also happens for base, for which
> >> our configuration is minimal.
> >> Did anyone inform them? Maybe it slipped through their monitoring.
> > It is still happening, see e.g.
> > https://github.com/macports/macports-ports/pull/1186
> This looks like a normal timeout.
> The build finished and I see no restarts.
Maybe I just don;t get the Travis terminology,
but it smultaneously finished _and_ timed out?
> The timeout after 50 minutes is expected.
> This is a limitation of Travis CI and cannot be increased.
Why? Surely it's a config constant.
> Pull requests for ports that need longer to build
> cannot be tested automatically.
So what should I do about e.g.
which needs loger to build because it touches lirc?
Currently, such PRs seem kinda discriminated with
"All checks have failed" (sounds horrible, right?)
eventhough it's just Travis timing out.
More information about the macports-dev