DPDK patches and discussions
 help / color / mirror / Atom feed
From: Aaron Conole <aconole@redhat.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Bruce Richardson <bruce.richardson@intel.com>,  dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [RFC 0/3] ci: enable unit tests for non-aarch64 platforms
Date: Tue, 02 Apr 2019 08:49:09 -0400	[thread overview]
Message-ID: <f7tsgv0mv22.fsf@dhcp-25.97.bos.redhat.com> (raw)
Message-ID: <20190402124909.mlEh1b3G7dIbsC2iVz5_mJ2lpYdSyvKJz2GPdcRxahk@z> (raw)
In-Reply-To: <CAJFAV8x-JHU3qDkxbenXG7nHFbVVs8eWGpkYAiMbEe_51HybgQ@mail.gmail.com> (David Marchand's message of "Tue, 2 Apr 2019 12:09:26 +0200")

David Marchand <david.marchand@redhat.com> writes:

> On Tue, Apr 2, 2019 at 11:37 AM Bruce Richardson <bruce.richardson@intel.com> wrote:
>
>  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@redhat.com> wrote:
>  > 
>  > > David Marchand <david.marchand@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.
>
> Hard to tell, I would have to retest and investigate, unless Aaron went further than me.

I did some investigation with this.  At least I don't see any lingering
process from meson, but it does take time for the tests to die when I
hit CTRL-C, and I get a warning - I found this related bug:
   https://github.com/mesonbuild/meson/issues/2281

I guess it could be some kind of interplay between the way meson kills
tests?  Looking at the commit that eventually 'closes' the bug, they
merely set a flag rather than pass a kill signal down, so I guess it's
probably never going to be immediate.

  parent reply	other threads:[~2019-04-02 12:49 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-29 17:22 Aaron Conole
2019-03-29 17:22 ` Aaron Conole
2019-03-29 17:22 ` [dpdk-dev] [RFC 1/3] test/meson: auto detect number of cores Aaron Conole
2019-03-29 17:22   ` Aaron Conole
2019-04-01 13:48   ` David Marchand
2019-04-01 13:48     ` David Marchand
2019-04-01 14:07     ` Aaron Conole
2019-04-01 14:07       ` Aaron Conole
2019-04-01 16:23   ` Pattan, Reshma
2019-04-01 16:23     ` Pattan, Reshma
2019-04-01 17:48     ` Aaron Conole
2019-04-01 17:48       ` Aaron Conole
2019-04-01 19:39       ` Thomas Monjalon
2019-04-01 19:39         ` Thomas Monjalon
2019-04-01 19:58         ` Aaron Conole
2019-04-01 19:58           ` Aaron Conole
2019-03-29 17:22 ` [dpdk-dev] [RFC 2/3] meson-tests: separate slower tests Aaron Conole
2019-03-29 17:22   ` Aaron Conole
2019-03-29 17:22 ` [dpdk-dev] [RFC 3/3] ci: enable tests on non-arm platforms Aaron Conole
2019-03-29 17:22   ` Aaron Conole
2019-04-17  8:32   ` Jerin Jacob Kollanukkaran
2019-04-17  8:32     ` Jerin Jacob Kollanukkaran
2019-04-17 12:39     ` Aaron Conole
2019-04-17 12:39       ` Aaron Conole
2019-04-17 15:32       ` [dpdk-dev] [EXT] " Jerin Jacob Kollanukkaran
2019-04-17 15:32         ` Jerin Jacob Kollanukkaran
2019-04-01 19:15 ` [dpdk-dev] [RFC 0/3] ci: enable unit tests for non-aarch64 platforms David Marchand
2019-04-01 19:15   ` David Marchand
2019-04-01 19:28   ` Aaron Conole
2019-04-01 19:28     ` Aaron Conole
2019-04-01 19:29     ` David Marchand
2019-04-01 19:29       ` David Marchand
2019-04-02  9:37       ` Bruce Richardson
2019-04-02  9:37         ` Bruce Richardson
2019-04-02 10:09         ` David Marchand
2019-04-02 10:09           ` David Marchand
2019-04-02 12:49           ` Aaron Conole [this message]
2019-04-02 12:49             ` Aaron Conole

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=f7tsgv0mv22.fsf@dhcp-25.97.bos.redhat.com \
    --to=aconole@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    /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).