[dpdk-dev] [RFC 0/3] ci: enable unit tests for non-aarch64 platforms

Bruce Richardson bruce.richardson at intel.com
Tue Apr 2 11:37:36 CEST 2019


On Mon, Apr 01, 2019 at 09:29:51PM +0200, David Marchand wrote:
> On Mon, Apr 1, 2019 at 9:28 PM Aaron Conole <aconole at redhat.com> wrote:
> 
> > David Marchand <david.marchand at redhat.com> writes:
> > > I tried using meson/ninja for the tests, something that bothered me is
> > that I can't interrupt the tests.
> > > I had to kill manually, meson, ninja and I had some leftover dpdk-test
> > processes (maybe due to some ^Z I
> > > hit...).
> > > Is this expected ?
> >
> > Certainly not by me.  I usually let everything complete, though (which
> > takes a looong time if I run the full suite).
> >
> > > This is quite frustrating when testing "before" and "after" each patch.
> >
> > Agreed.  :-/
> >
> > I'll have to try it out to see what's happening.  Does it only happen
> > with this series?  I'd be surprised, but possibly I introduced some error.
> >
> 
> Nop, I got this even before your first patch.
> 

Is this meson related or related to the auto test binary in DPDK. I know
traditionally I've found the test binary rather difficult to kill, but I'd
like to be sure that the meson infrastructure itself isn't making it worse.

/Bruce


More information about the dev mailing list