All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 742] intermittent func_reentrancy_autotest failures
Date: Thu, 17 Jun 2021 13:54:20 +0000	[thread overview]
Message-ID: <bug-742-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 742
           Summary: intermittent func_reentrancy_autotest failures
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: aconole@bytheb.org
  Target Milestone: ---

In the UNH IOL we see intermittent failures from the func_reentrancy_autotest
which happen regardless of platform.

Sometimes the report looks like:

(from https://lab.dpdk.org/results/dashboard/patchsets/17321/)

27/93 DPDK:fast-tests / func_reentrancy_autotest       FAIL           3.08s
(exit status 255 or signal 127 SIGinvalid)

--- command ---
07:03:58 DPDK_TEST='func_reentrancy_autotest'
/home-local/jenkins-local/jenkins-agent/workspace/Arm-gigabyte-Unit-Test-DPDK/dpdk/build/app/test/dpdk-test
-l 0-63 --file-prefix=func_reentrancy_autotest
--- stdout ---
RTE>>func_reentrancy_autotest
Too many lcores, some cores will be disabled
Func-ReEnt CASE 0: eal init once PASS
Func-ReEnt CASE 1: ring create/lookup PASS
Func-ReEnt CASE 2: mempool create/lookup FAIL
Test Failed
RTE>>

Sometimes it looks like:

--- command ---
12:35:49 DPDK_TEST='func_reentrancy_autotest'
/home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/build/app/test/dpdk-test
-l 0-15 --file-prefix=func_reentrancy_autotest
--- stdout ---
RTE>>func_reentrancy_autotest
--- stderr ---
EAL: Detected 16 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/func_reentrancy_autotest/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: No available 1048576 kB hugepages reported
EAL: VFIO support initialized
EAL:   Invalid NUMA socket, default to 0
APP: HPET is not enabled, using TSC as default timer
EAL: FATAL: already called initialization.
EAL: FATAL: already called initialization.
EAL: FATAL: already called initialization.
EAL: FATAL: already called initialization.
EAL: FATAL: already called initialization.
EAL: FATAL: already called initialization.
EAL: FATAL: already called initialization.
EAL: FATAL: already called initialization.
EAL: FATAL: already called initialization.
EAL: FATAL: already called initialization.
EAL: FATAL: already called initialization.
EAL: already called initialization.
EAL: FATAL: already called initialization.
EAL: FATAL: already called initialization.
EAL: already called initialization.
EAL: FATAL: already called initialization.
EAL: FATAL: already called initialization.
EAL: already called initialization.
EAL: already called initialization.
EAL: already called initialization.
EAL: already called initialization.
EAL: already called initialization.
EAL: already called initialization.
EAL: FATAL: already called initialization.
EAL: already called initialization.
EAL: already called initialization.
EAL: already called initialization.
EAL: already called initialization.
EAL: already called initialization.
EAL: already called initialization.
EAL: already called initialization.
EAL: already called initialization.
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
RING: Cannot reserve memory
-------

Probably there is some issue allocating memory but not enough information is
being captured.

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

                 reply	other threads:[~2021-06-17 13:54 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-742-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.