From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by dpdk.org (Postfix) with ESMTP id 9DD2C2BB0 for ; Thu, 9 Aug 2018 18:17:28 +0200 (CEST) X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Aug 2018 09:17:26 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.53,215,1531810800"; d="scan'208";a="252735290" Received: from bricha3-mobl.ger.corp.intel.com ([10.237.221.107]) by fmsmga005.fm.intel.com with SMTP; 09 Aug 2018 09:17:24 -0700 Received: by (sSMTP sendmail emulation); Thu, 09 Aug 2018 17:17:23 +0100 Date: Thu, 9 Aug 2018 17:17:23 +0100 From: Bruce Richardson To: "Burakov, Anatoly" Cc: Vivian Kong , dev@dpdk.org Message-ID: <20180809161722.GA14668@bricha3-MOBL.ger.corp.intel.com> References: <3fa3162e-9440-a957-4aa1-0f437e245ba2@intel.com> <8d982053-4e32-9dbe-fe76-f42bedd52fb5@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8d982053-4e32-9dbe-fe76-f42bedd52fb5@intel.com> Organization: Intel Research and Development Ireland Ltd. User-Agent: Mutt/1.10.1 (2018-07-13) Subject: Re: [dpdk-dev] How to run tests 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: Thu, 09 Aug 2018 16:17:29 -0000 On Thu, Aug 09, 2018 at 04:54:36PM +0100, Burakov, Anatoly wrote: > On 09-Aug-18 2:54 PM, Vivian Kong wrote: > > Thanks Anatoly. > > > > Is there a set of tests I can run to verify the build? > > Generally, most unit tests in the test app will do what you require. > Additionally, if you're using make build system, you can run "make test" and > it'll run an autotest script. Some tests may fail for various reasons > (additional setup requirements for KNI tests, multiprocess issues affecting > EAL flags and multiprocess autotests...), but generally that command can be > used to "verify the build". > > That said, it is by no means an exhaustive test, because most of DPDK > functionality of interest will require setting up traffic forwarding - unit > tests do very limited testing of that for obvious reasons. > Just FYI: As well as "make test", for meson builds you can also use "meson test", or "meson test " to run just one specific test.