From: David Marchand <david.marchand@redhat.com>
To: Aaron Conole <aconole@redhat.com>, Michael Santana <msantana@redhat.com>
Cc: dev <dev@dpdk.org>, Bruce Richardson <bruce.richardson@intel.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Luca Boccassi <bluca@debian.org>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH v2 0/2] Enable fast-unit tests under travis
Date: Mon, 5 Aug 2019 08:26:49 +0200 [thread overview]
Message-ID: <CAJFAV8z2oJ6ti1rWT_+mzTqK=7K9iP9f0BFhfjukxGu=ysEOrQ@mail.gmail.com> (raw)
In-Reply-To: <1865053.T8TvltaDb9@xps>
On Sat, Aug 3, 2019 at 12:00 AM Thomas Monjalon <thomas@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.
--
David Marchand
next prev parent reply other threads:[~2019-08-05 6:27 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 14:50 [dpdk-dev] [PATCH " Aaron Conole
2019-07-31 14:50 ` [dpdk-dev] [PATCH 1/2] tests: Fix unit tests for shared builds Aaron Conole
2019-07-31 15:36 ` Bruce Richardson
2019-07-31 16:07 ` Aaron Conole
2019-07-31 16:10 ` Aaron Conole
2019-08-01 9:19 ` Bruce Richardson
2019-08-01 15:40 ` Aaron Conole
2019-08-01 16:51 ` Bruce Richardson
2019-08-01 16:52 ` Bruce Richardson
2019-08-02 20:32 ` Thomas Monjalon
2019-08-02 20:43 ` Aaron Conole
2019-07-31 14:50 ` [dpdk-dev] [PATCH 2/2] ci: enable unit tests under travis-ci Aaron Conole
2019-07-31 20:54 ` Michael Santana Francisco
2019-08-02 13:34 ` Aaron Conole
2019-08-02 13:40 ` Michael Santana Francisco
2019-08-02 20:27 ` Thomas Monjalon
2019-08-02 20:59 ` Aaron Conole
2019-08-02 21:05 ` Thomas Monjalon
2019-08-02 21:07 ` Aaron Conole
2019-08-02 14:18 ` [dpdk-dev] [PATCH 0/2] Enable fast-unit tests under travis David Marchand
2019-08-02 21:25 ` [dpdk-dev] [PATCH v2 " Aaron Conole
2019-08-02 21:25 ` [dpdk-dev] [PATCH v2 1/2] tests: Fix unit tests for shared builds Aaron Conole
2019-08-02 21:51 ` Thomas Monjalon
2019-08-02 21:25 ` [dpdk-dev] [PATCH v2 2/2] ci: enable unit tests under travis-ci Aaron Conole
2019-08-02 22:00 ` [dpdk-dev] [PATCH v2 0/2] Enable fast-unit tests under travis Thomas Monjalon
2019-08-05 6:26 ` David Marchand [this message]
2019-08-05 12:52 ` David Marchand
2019-08-05 13:56 ` Michael Santana Francisco
2019-08-05 14:18 ` Aaron Conole
2019-08-05 14:21 ` Thomas Monjalon
2019-08-07 14:06 ` Michael Santana Francisco
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJFAV8z2oJ6ti1rWT_+mzTqK=7K9iP9f0BFhfjukxGu=ysEOrQ@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=msantana@redhat.com \
--cc=thomas@monjalon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).