From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vs1-f53.google.com (mail-vs1-f53.google.com [209.85.217.53]) by dpdk.org (Postfix) with ESMTP id 09D042B99 for ; Tue, 2 Apr 2019 12:09:38 +0200 (CEST) Received: by mail-vs1-f53.google.com with SMTP id f15so7385768vsk.9 for ; Tue, 02 Apr 2019 03:09:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=dRzsoDXiypTobnm68KMmqNufccy6wTpIPv4dOnM8F/Q=; b=PwY/MIWYtm+rPC3WSD5ah4bxfBd0fV16O3lMqNj3LWz3PasPQCIY3ouFMmulVZA27J kyLu36LQsTCQnf57aoBmPFKxBb7QOK8dkdIka9NbtO/eZt1gu3xhDUvB+d8oJ7mtKIHM iRNqNNNaemdZguJWC7nIcd2ojmC6Kv8aykEgiQxYFMgUkj+xebSinMdk31/yR2Z8gAQv UBnS7sK/5yi01OjFYTQ2slXUYpGJtX03cPmc0fkd8kafAJs6EiTFO6O0DUw2XviFx1qy n1MTNmUL4jkFAGKKVOwEpFJbvdmZcRILBiMQM6q1Vtw7HWnE1H4HL3b5wSFsiUGl1Y6D LF1g== X-Gm-Message-State: APjAAAVZZdRtEBPqnrDCygJl3HjHJ8QHID3iitxduATVHJuDh4Qs0Qqj WTUddmFyI3Njx7nLjiiBuj3/MS1HH9X6BNYwxjwvnw== X-Google-Smtp-Source: APXvYqwensZfFEMhnh/c2yw4Qp5pkbXd3VcZu12c3xUztguDhZ2eQavm+pTKBKRxzh/cRSa9DRYMAP0qQ5GCswRoRRE= X-Received: by 2002:a67:c812:: with SMTP id u18mr1794508vsk.87.1554199777470; Tue, 02 Apr 2019 03:09:37 -0700 (PDT) MIME-Version: 1.0 References: <20190329172241.11916-1-aconole@redhat.com> <20190402093736.GC1470@bricha3-MOBL.ger.corp.intel.com> In-Reply-To: <20190402093736.GC1470@bricha3-MOBL.ger.corp.intel.com> From: David Marchand Date: Tue, 2 Apr 2019 12:09:26 +0200 Message-ID: To: Bruce Richardson Cc: Aaron Conole , dev Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 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 10:09:38 -0000 On Tue, Apr 2, 2019 at 11:37 AM Bruce Richardson 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 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. > Hard to tell, I would have to retest and investigate, unless Aaron went further than me. -- David Marchand 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 B6306A0679 for ; Tue, 2 Apr 2019 12:09:39 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id BAFBE3576; Tue, 2 Apr 2019 12:09:38 +0200 (CEST) Received: from mail-vs1-f53.google.com (mail-vs1-f53.google.com [209.85.217.53]) by dpdk.org (Postfix) with ESMTP id 09D042B99 for ; Tue, 2 Apr 2019 12:09:38 +0200 (CEST) Received: by mail-vs1-f53.google.com with SMTP id f15so7385768vsk.9 for ; Tue, 02 Apr 2019 03:09:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=dRzsoDXiypTobnm68KMmqNufccy6wTpIPv4dOnM8F/Q=; b=PwY/MIWYtm+rPC3WSD5ah4bxfBd0fV16O3lMqNj3LWz3PasPQCIY3ouFMmulVZA27J kyLu36LQsTCQnf57aoBmPFKxBb7QOK8dkdIka9NbtO/eZt1gu3xhDUvB+d8oJ7mtKIHM iRNqNNNaemdZguJWC7nIcd2ojmC6Kv8aykEgiQxYFMgUkj+xebSinMdk31/yR2Z8gAQv UBnS7sK/5yi01OjFYTQ2slXUYpGJtX03cPmc0fkd8kafAJs6EiTFO6O0DUw2XviFx1qy n1MTNmUL4jkFAGKKVOwEpFJbvdmZcRILBiMQM6q1Vtw7HWnE1H4HL3b5wSFsiUGl1Y6D LF1g== X-Gm-Message-State: APjAAAVZZdRtEBPqnrDCygJl3HjHJ8QHID3iitxduATVHJuDh4Qs0Qqj WTUddmFyI3Njx7nLjiiBuj3/MS1HH9X6BNYwxjwvnw== X-Google-Smtp-Source: APXvYqwensZfFEMhnh/c2yw4Qp5pkbXd3VcZu12c3xUztguDhZ2eQavm+pTKBKRxzh/cRSa9DRYMAP0qQ5GCswRoRRE= X-Received: by 2002:a67:c812:: with SMTP id u18mr1794508vsk.87.1554199777470; Tue, 02 Apr 2019 03:09:37 -0700 (PDT) MIME-Version: 1.0 References: <20190329172241.11916-1-aconole@redhat.com> <20190402093736.GC1470@bricha3-MOBL.ger.corp.intel.com> In-Reply-To: <20190402093736.GC1470@bricha3-MOBL.ger.corp.intel.com> From: David Marchand Date: Tue, 2 Apr 2019 12:09:26 +0200 Message-ID: To: Bruce Richardson Cc: Aaron Conole , dev Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 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: <20190402100926.UnVy_rhlfgOxKtyhqRWS2BGy-1It61MH0asHr3pRJkU@z> On Tue, Apr 2, 2019 at 11:37 AM Bruce Richardson 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 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. > Hard to tell, I would have to retest and investigate, unless Aaron went further than me. -- David Marchand