tinkerpop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephen Mallette <spmalle...@gmail.com>
Subject Re: Travis Job Naming
Date Mon, 10 Jun 2019 10:34:42 GMT
Yeah...I was aware of the loss of complete parallelism I guess. Logically,
if the first stage failed then the second stage wasn't worth even trying
with similar logic for the third. But, perhaps it's all just a single
"Testing" stage. I'll change it.

On Mon, Jun 10, 2019 at 4:36 AM Jorge Bay Gondra <jorgebaygondra@gmail.com>
wrote:

> Oh looks way cleaner! Thanks!
>
> One thing we lost with this layout is the ability to run multiple test
> groups in parallel, build time went from ~42mins
> <https://travis-ci.org/apache/tinkerpop/builds/534940067> to 1h19m
> <https://travis-ci.org/apache/tinkerpop/builds/543397816>.
>
> The underlying reason is that TravisCI runs one stage after another
> sequentially. We could group them into the same stage to get them to start
> in parallel.
>
> On Fri, Jun 7, 2019 at 9:44 PM Stephen Mallette <spmallette@gmail.com>
> wrote:
>
> > I've long been tired of seeing a failing job in Travis and then just
> seeing
> > a red "X" and a job number and then having to scroll through the log
> output
> > to figure out which particular build job failed. was it python? was it
> > .NET? was it just regular ol' mvn clean install?
> >
> > Well, I've managed to make some improvements and figured out how to stage
> > test runs into groups and then assign names to them - here's an example
> of
> > what it looks like now:
> >
> > https://travis-ci.org/apache/tinkerpop/builds/542862332
> >
> > Now, you see an "X", you immediately know what tanked. excellent
> >
>

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