From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 64D3F160 for ; Mon, 18 Dec 2017 16:24:19 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Dec 2017 07:24:19 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.45,422,1508828400"; d="scan'208";a="13307021" Received: from irsmsx107.ger.corp.intel.com ([163.33.3.99]) by orsmga003.jf.intel.com with ESMTP; 18 Dec 2017 07:24:18 -0800 Received: from irsmsx102.ger.corp.intel.com ([169.254.2.180]) by IRSMSX107.ger.corp.intel.com ([169.254.10.239]) with mapi id 14.03.0319.002; Mon, 18 Dec 2017 15:24:17 +0000 From: "Van Haaren, Harry" To: "Richardson, Bruce" CC: "dev@dpdk.org" Thread-Topic: [PATCH 0/2] next-build: add test app to build Thread-Index: AQHTd/bogAS+sGDzoES5JcWmSkKHmqNJIFOAgAAP40A= Date: Mon, 18 Dec 2017 15:24:16 +0000 Message-ID: References: <1513598038-148115-1-git-send-email-harry.van.haaren@intel.com> <20171218135723.GC15444@bricha3-MOBL3.ger.corp.intel.com> In-Reply-To: <20171218135723.GC15444@bricha3-MOBL3.ger.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYjc0ZWQxN2QtOWViOC00OWZlLThiMTItZGY0ZGE1ZWZkMmMxIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX1BVQkxJQyJ9XX1dfSwiU3ViamVjdExhYmVscyI6W10sIlRNQ1ZlcnNpb24iOiIxNi41LjkuMyIsIlRydXN0ZWRMYWJlbEhhc2giOiJvME9QajFkTTROVmlHR0ZWY3pUYWRPODE2eEdOUzN4eHVlcVRHNjJQQ2QwPSJ9 x-ctpclassification: CTP_PUBLIC dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [163.33.239.181] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH 0/2] next-build: add test app to build 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, 18 Dec 2017 15:24:20 -0000 > From: Richardson, Bruce > Sent: Monday, December 18, 2017 1:57 PM > To: Van Haaren, Harry > Cc: dev@dpdk.org > Subject: Re: [PATCH 0/2] next-build: add test app to build >=20 > On Mon, Dec 18, 2017 at 11:53:56AM +0000, Harry van Haaren wrote: > > This patchset adds the test/test/test app to the Meson build. > > In doing so, the test app is improved to allow running a unit > > test by setting an environment variable. This allows the meson > > test infrastructure to integrate with the DPDK tests. Some nice > > improvements from the above integration, including debug aids... > > > > Run all autotests: > > $ meson test > > >=20 > meson or ninja? meson. If I'm understanding correctly the "meson test" command invokes the ninja test runner, however some of the argument mushing (eg: --gdb) is performed by meson before launching ninja. > > Run a specific test: > > $ meson test ring_perf_autotest > > > > Run a specific test multiple times, eg brute-forcing race conditions: > > $ meson test eventdev_sw_autotest --repeat=3D3 > > > > Run a specific test multiple times in gdb, eg to drop to GDB if race > found: > > $ meson test eventdev_sw_autotest --repeat=3D3 --gdb > > >=20 > The "repeat" and "gdb" arguments come built-in in meson, right, not from > this patchset? Yes correct, Meson provides this functionality.