From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [dpdk-stable] [PATCH] test-meson-build: fix check for whether meson has run Date: Mon, 14 Jan 2019 12:19:08 +0100 Message-ID: <16471174.gmsOdrL8Yx@xps> References: <20190110103726.23231-1-bruce.richardson@intel.com> <1547125801.16085.2.camel@debian.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: stable@dpdk.org, Luca Boccassi , dev@dpdk.org To: Bruce Richardson Return-path: In-Reply-To: <1547125801.16085.2.camel@debian.org> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 10/01/2019 14:10, Luca Boccassi: > On Thu, 2019-01-10 at 10:37 +0000, Bruce Richardson wrote: > > The current check to see whether we need to call meson or just ninja > > simply checked if the build directory existed. However, if meson was > > run > > but failed, the build directory would still exist. We can fix this by > > instead checking for the build.ninja file inside the directory. Once > > that > > is present, we can use ninja safely and let it worry about rerunning > > meson if necessary. > > > > Fixes: a55277a788df ("devtools: add test script for meson builds") > > CC: stable@dpdk.org > > > > Signed-off-by: Bruce Richardson > > Acked-by: Luca Boccassi Applied, thanks