On Mon, Aug 5, 2019 at 8:52 AM David Marchand <david.march...@redhat.com> wrote:
>
> On Mon, Aug 5, 2019 at 8:26 AM David Marchand <david.march...@redhat.com>
> wrote:
> >
> > On Sat, Aug 3, 2019 at 12:00 AM Thomas Monjalon <tho...@monjalon.net> wrote:
> > >
> > > 02/08/2019 23:25, Aaron Conole:
> > > > This series turns the fast unit tests on for a limited set of
> > > > builds under the travis build system. An example run is available
> > > > at:
> > > >
> > > > https://travis-ci.org/orgcandman/dpdk/builds/565991679
> > > >
> > > > The builds which execute the unit tests may be distinguished by the
> > > > "RUN_TESTS" parameter.
> > > >
> > > > Aaron Conole (1):
> > > > ci: enable unit tests under travis-ci
> > > >
> > > > Michael Santana (1):
> > > > tests: Fix unit tests for shared builds
> > >
> > > Applied with change in comments of first patch, as described in this
> > > thread.
> > > Thanks
> >
> > Not sure I understand this error:
> > https://travis-ci.com/DPDK/dpdk/jobs/222141682
> >
> > The 'static' config worked fine:
> > https://travis-ci.com/DPDK/dpdk/jobs/222141683
> >
> >
> > Maybe a network issue ? But I would expect some kind of related
> > warning/error message.
It's either that or some other issue with the travis infrastructure.
There is nothing wrong in our end which is the frustrating part. I am
being hopeful and optimistic that it's _just a hiccup_ and it will go
away on its own. If it really keeps happening then we might need to
report the issue to travis
> >
>
> Ah something like those messages:
> https://travis-ci.com/DPDK/dpdk/jobs/222407326
> https://travis-ci.com/DPDK/dpdk/jobs/222417471
>
> Is there a way to retry builds?
Yes, at the very top, to the right there is a 'Restart job' button.
You have to be logged in as the owner of the repo to be able to see it
and click on it. That will restart the job from the very start.
> Automatically?
That's the million dollar question. We'll have to investigate if it's possible
>
>
> --
> David Marchand
