[dpdk-dev] Encountering ninja test failures?

Aaron Conole aconole at redhat.com
Thu Feb 28 23:08:52 CET 2019


David Marchand <david.marchand at redhat.com> writes:

> On Thu, Feb 28, 2019 at 10:31 PM Aaron Conole <aconole at 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.


More information about the dev mailing list