arrow-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jacques Nadeau <jacq...@apache.org>
Subject Re: CI reliability?
Date Tue, 25 Jul 2017 00:24:21 GMT
Got it, thanks Wes. I haven't been working with travis for retriggering so
didn't know if there was something more elegant.

On Mon, Jul 24, 2017 at 4:01 PM, Wes McKinney <wesmckinn@gmail.com> wrote:

> That particular job is timing out because it's configured in a way
> that's causing various steps to be recomputed
>
> https://issues.apache.org/jira/browse/ARROW-1253
>
> I plan to fix it as soon as I can get the package builds for 0.5.0
> sorted out, maybe later tonight, but have already been working around
> the clock as it is.
>
> Generally the CI has been pretty reliable; occasionally we get a
> Homebrew timeout or some other flakiness that's related to Travis CI
> infrastructure.
>
> If you're concerned about whether you've broken a build I usually do
> git commit --amend to re-trigger the build.
>
> On Mon, Jul 24, 2017 at 6:15 PM, Jacques Nadeau <jacques@apache.org>
> wrote:
> > Hey All,
> >
> > I'm wondering how reliable the CI stuff has been. I just saw a ci job
> that
> > was terminated due to time limits. Is that a common occurrence? Is there
> an
> > easy way to retrigger?
> >
> > https://travis-ci.org/apache/arrow/builds/257002967
> >
> > thanks,
> > Jacques
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message