* [dpdk-dev] [Bug 742] intermittent func_reentrancy_autotest failures
@ 2021-06-17 13:54 bugzilla
0 siblings, 0 replies; only message in thread
From: bugzilla @ 2021-06-17 13:54 UTC (permalink / raw)
To: dev
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.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2021-06-17 13:54 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-06-17 13:54 [dpdk-dev] [Bug 742] intermittent func_reentrancy_autotest failures bugzilla
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).