From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vk1-f169.google.com (mail-vk1-f169.google.com [209.85.221.169]) by dpdk.org (Postfix) with ESMTP id D23F93572 for ; Mon, 1 Apr 2019 21:30:02 +0200 (CEST) Received: by mail-vk1-f169.google.com with SMTP id v131so2391721vkd.3 for ; Mon, 01 Apr 2019 12:30:02 -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=cU0y3SoT+kGnmascMfTyI5vYyLHoWoNWPI4cfbYw2bA=; b=h7rBzrmbUcuFfXyRIzZWk9B0LxHO9FxqqJzs4osCz8HpDIkZFkBHxfSOMsleggdGYC zpPTBSwgqrkvMd1zK/UQ8/BajSGNVOIMSCTCZ6aODvt9DvbcHGkLE22EUEOg9WoyWpVD VvrAGRKdXh6HQPHvC3DawlKQsFIN06CSDIn4Tv+HrDiHDOANT3JK7PDQKYByZcBQnBdz oxWVKtWza5PF96EfaNvkM5mjj83gwNvOlRDouJ2m0rrsyvCk9gM5zn4/xrhf0pX7UHef 2tEyKQ8w8luid2xkJwrEpgGIkwNtKv9n6EjxlWdb3wcyUK7Fs4DmNHF4m+q+h/sGjPW+ fU9w== X-Gm-Message-State: APjAAAUvSqZn/C8ql7Kq/4ZJLbaRP14IukzfZW77uXCrPEKXwhQd9NHM z/0G8DpLl6lZ45sfy3U0v3xyWLBTouevMmpHtIOTcA== X-Google-Smtp-Source: APXvYqyLZAzlPT0XvAYEVsnr4jsXUjObNJBpiHQ8MYVLDSuph5OIXHY4HwUq2Cck4frG6uqQsx350RFBczYP6srTL+M= X-Received: by 2002:a1f:bf4b:: with SMTP id p72mr20408418vkf.77.1554147002282; Mon, 01 Apr 2019 12:30:02 -0700 (PDT) MIME-Version: 1.0 References: <20190329172241.11916-1-aconole@redhat.com> In-Reply-To: From: David Marchand Date: Mon, 1 Apr 2019 21:29:51 +0200 Message-ID: To: Aaron Conole Cc: 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: Mon, 01 Apr 2019 19:30:03 -0000 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. -- 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 19F3BA0679 for ; Mon, 1 Apr 2019 21:30:04 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id CFAC33576; Mon, 1 Apr 2019 21:30:03 +0200 (CEST) Received: from mail-vk1-f169.google.com (mail-vk1-f169.google.com [209.85.221.169]) by dpdk.org (Postfix) with ESMTP id D23F93572 for ; Mon, 1 Apr 2019 21:30:02 +0200 (CEST) Received: by mail-vk1-f169.google.com with SMTP id v131so2391721vkd.3 for ; Mon, 01 Apr 2019 12:30:02 -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=cU0y3SoT+kGnmascMfTyI5vYyLHoWoNWPI4cfbYw2bA=; b=h7rBzrmbUcuFfXyRIzZWk9B0LxHO9FxqqJzs4osCz8HpDIkZFkBHxfSOMsleggdGYC zpPTBSwgqrkvMd1zK/UQ8/BajSGNVOIMSCTCZ6aODvt9DvbcHGkLE22EUEOg9WoyWpVD VvrAGRKdXh6HQPHvC3DawlKQsFIN06CSDIn4Tv+HrDiHDOANT3JK7PDQKYByZcBQnBdz oxWVKtWza5PF96EfaNvkM5mjj83gwNvOlRDouJ2m0rrsyvCk9gM5zn4/xrhf0pX7UHef 2tEyKQ8w8luid2xkJwrEpgGIkwNtKv9n6EjxlWdb3wcyUK7Fs4DmNHF4m+q+h/sGjPW+ fU9w== X-Gm-Message-State: APjAAAUvSqZn/C8ql7Kq/4ZJLbaRP14IukzfZW77uXCrPEKXwhQd9NHM z/0G8DpLl6lZ45sfy3U0v3xyWLBTouevMmpHtIOTcA== X-Google-Smtp-Source: APXvYqyLZAzlPT0XvAYEVsnr4jsXUjObNJBpiHQ8MYVLDSuph5OIXHY4HwUq2Cck4frG6uqQsx350RFBczYP6srTL+M= X-Received: by 2002:a1f:bf4b:: with SMTP id p72mr20408418vkf.77.1554147002282; Mon, 01 Apr 2019 12:30:02 -0700 (PDT) MIME-Version: 1.0 References: <20190329172241.11916-1-aconole@redhat.com> In-Reply-To: From: David Marchand Date: Mon, 1 Apr 2019 21:29:51 +0200 Message-ID: To: Aaron Conole Cc: 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: <20190401192951.UriIv1Mdi1ki1829IgWueTrFJFtj17nYvJwGh8rlBpg@z> 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. -- David Marchand