[dpdk-dev] [PATCH v2 0/2] Enable fast-unit tests under travis

Aaron Conole aconole at redhat.com
Mon Aug 5 16:18:52 CEST 2019


Michael Santana Francisco <msantana at redhat.com> writes:

> On Mon, Aug 5, 2019 at 8:52 AM David Marchand <david.marchand at redhat.com> wrote:
>>
>> On Mon, Aug 5, 2019 at 8:26 AM David Marchand <david.marchand at redhat.com> wrote:
>> >
>> > On Sat, Aug 3, 2019 at 12:00 AM Thomas Monjalon <thomas at 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

It's possible.  I need to get the robot polling travis correctly still.

At the moment it can poll, but we don't have enough of the data
recorded.  It's coming though.

One thing I notice is that some of the tests are still failing
'sporadically' and that's difficult to discern.  So we might just use
the robot as 'warn' rather than 'error' for now and maintainers will
have to make a best determination.

>>
>>
>> --
>> David Marchand


More information about the dev mailing list