From: "Pattan, Reshma" <reshma.pattan@intel.com>
To: Aaron Conole <aconole@redhat.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Babu Radhakrishnan,
AgalyaX" <agalyax.babu.radhakrishnan@intel.com>,
"Parthasarathy, JananeeX M" <jananeex.m.parthasarathy@intel.com>
Subject: Re: [dpdk-dev] [RFC 1/3] test/meson: auto detect number of cores
Date: Mon, 1 Apr 2019 16:23:07 +0000 [thread overview]
Message-ID: <3AEA2BF9852C6F48A459DA490692831F2A433A0F@irsmsx110.ger.corp.intel.com> (raw)
Message-ID: <20190401162307.t22lHVx5i7cZ2hESP4bAezGJQ_hKip_OnvuxHjuK5hA@z> (raw)
In-Reply-To: <20190329172241.11916-2-aconole@redhat.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Aaron Conole
> Sent: Friday, March 29, 2019 5:23 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [RFC 1/3] test/meson: auto detect number of cores
>
> Some environments do not provide a minimum 4 cores for running tests. This
> allows those environments to still execute 'ninja test' without causing multiple
> failures.
>
FYI, there is a patch http://patches.dpdk.org/patch/50850/ doing something similar.
--file-prefix is not supported on FreeBSD, so how about you also include the related fix from above patch link into your patch series?
Thanks,
Reshma
next prev parent reply other threads:[~2019-04-01 16:23 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 17:22 [dpdk-dev] [RFC 0/3] ci: enable unit tests for non-aarch64 platforms Aaron Conole
2019-03-29 17:22 ` Aaron Conole
2019-03-29 17:22 ` [dpdk-dev] [RFC 1/3] test/meson: auto detect number of cores Aaron Conole
2019-03-29 17:22 ` Aaron Conole
2019-04-01 13:48 ` David Marchand
2019-04-01 13:48 ` David Marchand
2019-04-01 14:07 ` Aaron Conole
2019-04-01 14:07 ` Aaron Conole
2019-04-01 16:23 ` Pattan, Reshma [this message]
2019-04-01 16:23 ` Pattan, Reshma
2019-04-01 17:48 ` Aaron Conole
2019-04-01 17:48 ` Aaron Conole
2019-04-01 19:39 ` Thomas Monjalon
2019-04-01 19:39 ` Thomas Monjalon
2019-04-01 19:58 ` Aaron Conole
2019-04-01 19:58 ` Aaron Conole
2019-03-29 17:22 ` [dpdk-dev] [RFC 2/3] meson-tests: separate slower tests Aaron Conole
2019-03-29 17:22 ` Aaron Conole
2019-03-29 17:22 ` [dpdk-dev] [RFC 3/3] ci: enable tests on non-arm platforms Aaron Conole
2019-03-29 17:22 ` Aaron Conole
2019-04-17 8:32 ` Jerin Jacob Kollanukkaran
2019-04-17 8:32 ` Jerin Jacob Kollanukkaran
2019-04-17 12:39 ` Aaron Conole
2019-04-17 12:39 ` Aaron Conole
2019-04-17 15:32 ` [dpdk-dev] [EXT] " Jerin Jacob Kollanukkaran
2019-04-17 15:32 ` Jerin Jacob Kollanukkaran
2019-04-01 19:15 ` [dpdk-dev] [RFC 0/3] ci: enable unit tests for non-aarch64 platforms David Marchand
2019-04-01 19:15 ` David Marchand
2019-04-01 19:28 ` Aaron Conole
2019-04-01 19:28 ` Aaron Conole
2019-04-01 19:29 ` David Marchand
2019-04-01 19:29 ` David Marchand
2019-04-02 9:37 ` Bruce Richardson
2019-04-02 9:37 ` Bruce Richardson
2019-04-02 10:09 ` David Marchand
2019-04-02 10:09 ` David Marchand
2019-04-02 12:49 ` Aaron Conole
2019-04-02 12:49 ` Aaron Conole
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3AEA2BF9852C6F48A459DA490692831F2A433A0F@irsmsx110.ger.corp.intel.com \
--to=reshma.pattan@intel.com \
--cc=aconole@redhat.com \
--cc=agalyax.babu.radhakrishnan@intel.com \
--cc=dev@dpdk.org \
--cc=jananeex.m.parthasarathy@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).