DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 952] unit tests fail when machine has more than 128 cores
Date: Mon, 07 Mar 2022 13:28:21 +0000	[thread overview]
Message-ID: <bug-952-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=952

            Bug ID: 952
           Summary: unit tests fail when machine has more than 128 cores
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: other
          Assignee: dev@dpdk.org
          Reporter: luca.boccassi@gmail.com
  Target Milestone: ---

|  1/54 DPDK:fast-tests / bitops_autotest          RUNNING       
| >>> DPDK_TEST=bitops_autotest MALLOC_PERTURB_=20
/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/app/test/dpdk-test '-l 0-143' --no-huge
-m 2048 --file-prefix=bitops_autotest
| 
| EAL: Detected 128 lcore(s)
| EAL: Detected 4 NUMA nodes
| EAL: invalid core list syntax
| EAL: FATAL: Invalid 'command line' arguments.
| EAL: Invalid 'command line' arguments.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006341

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2022-03-07 13:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-952-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@dpdk.org \
    /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).