From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id 1C990378B for ; Tue, 2 Apr 2019 11:37:41 +0200 (CEST) X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Apr 2019 02:37:41 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,300,1549958400"; d="scan'208";a="332957921" Received: from bricha3-mobl.ger.corp.intel.com ([10.237.221.35]) by fmsmga006.fm.intel.com with SMTP; 02 Apr 2019 02:37:39 -0700 Received: by (sSMTP sendmail emulation); Tue, 02 Apr 2019 10:37:37 +0100 Date: Tue, 2 Apr 2019 10:37:36 +0100 From: Bruce Richardson To: David Marchand Cc: Aaron Conole , dev Message-ID: <20190402093736.GC1470@bricha3-MOBL.ger.corp.intel.com> References: <20190329172241.11916-1-aconole@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.4 (2019-03-13) Subject: Re: [dpdk-dev] [RFC 0/3] ci: enable unit tests for non-aarch64 platforms X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Apr 2019 09:37:42 -0000 On Mon, Apr 01, 2019 at 09:29:51PM +0200, David Marchand wrote: > On Mon, Apr 1, 2019 at 9:28 PM Aaron Conole wrote: > > > David Marchand 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id C1A4AA0679 for ; Tue, 2 Apr 2019 11:37:44 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id A054C4C91; Tue, 2 Apr 2019 11:37:43 +0200 (CEST) Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id 1C990378B for ; Tue, 2 Apr 2019 11:37:41 +0200 (CEST) X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Apr 2019 02:37:41 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,300,1549958400"; d="scan'208";a="332957921" Received: from bricha3-mobl.ger.corp.intel.com ([10.237.221.35]) by fmsmga006.fm.intel.com with SMTP; 02 Apr 2019 02:37:39 -0700 Received: by (sSMTP sendmail emulation); Tue, 02 Apr 2019 10:37:37 +0100 Date: Tue, 2 Apr 2019 10:37:36 +0100 From: Bruce Richardson To: David Marchand Cc: Aaron Conole , dev Message-ID: <20190402093736.GC1470@bricha3-MOBL.ger.corp.intel.com> References: <20190329172241.11916-1-aconole@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.4 (2019-03-13) Subject: Re: [dpdk-dev] [RFC 0/3] ci: enable unit tests for non-aarch64 platforms X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Message-ID: <20190402093736.Qbp3xb9zvRWnM7TeZ4ka1S3jVSrxRQeN0Une-f9D5Zs@z> On Mon, Apr 01, 2019 at 09:29:51PM +0200, David Marchand wrote: > On Mon, Apr 1, 2019 at 9:28 PM Aaron Conole wrote: > > > David Marchand 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