From: Aaron Conole <aconole@redhat.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>,
Michael Santana <msantana@redhat.com>
Subject: Re: [dpdk-dev] Encountering ninja test failures?
Date: Thu, 28 Feb 2019 17:08:52 -0500 [thread overview]
Message-ID: <f7twoljo9aj.fsf@dhcp-25.97.bos.redhat.com> (raw)
In-Reply-To: <CAJFAV8wmSaL_AdDT6P5p2eGZC6sWBZy2vP-eaidJJ00Sf61YFQ@mail.gmail.com> (David Marchand's message of "Thu, 28 Feb 2019 22:44:10 +0100")
David Marchand <david.marchand@redhat.com> writes:
> On Thu, Feb 28, 2019 at 10:31 PM Aaron Conole <aconole@redhat.com> wrote:
>
> Greetings dev,
>
> I'm trying to test out the latest iteration of travis support, and as
> part of that I've added the ability to execute tests.
>
> I can't seem to get the tests to execute correctly under travis. The
> build I have is here:
>
> https://travis-ci.org/orgcandman/dpdk/jobs/500014191
>
> Based on this commit:
>
> https://github.com/orgcandman/dpdk/tree/travis_v5
>
> which is cut from dpdk/master
>
> Anyone else see this? Maybe I missed something?
>
> DPDK_TEST='acl_autotest' /home/travis/build/orgcandman/dpdk/build/app/test/dpdk-test -c f -n 4 --file-prefix=acl_autotest
> EAL: Detected 2 lcore(s)
> EAL: Detected 1 NUMA nodes
> EAL: lcore 2 unavailable
> EAL: invalid coremask
> EAL: FATAL: Invalid 'command line' arguments.
> EAL: Invalid 'command line' arguments.
> The test app asked for 4 cores (0xf mask), but only two are available.
Thanks, David! Looks like it's hard coded in the meson.build
Okay, I'll be spinning a patch.
prev parent reply other threads:[~2019-02-28 22:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 21:31 Aaron Conole
2019-02-28 21:44 ` David Marchand
2019-02-28 22:08 ` Aaron Conole [this message]
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=f7twoljo9aj.fsf@dhcp-25.97.bos.redhat.com \
--to=aconole@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=msantana@redhat.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).