[Bug 1107] [22.11-rc1][meson test] seqlock_autotest test failed

[bugzilla at dpdk.org]

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

            Bug ID: 1107
           Summary: [22.11-rc1][meson test] seqlock_autotest test failed
           Product: DPDK
           Version: 22.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: meson
          Assignee: dev at dpdk.org
          Reporter: yux.jiang at intel.com
  Target Milestone: ---

[Environment]
DPDK version: dpdk22.11.0rc1 a74b1b25136a592c275afbfa6b70771469750aee
OS: CentOS7.9/3.10.0-1160.62.1.el7.x86_64 or 3.10.0-1160.71.1.el7.x86_64
Compiler: gcc version 4.8.5 20150623
Hardware platform: Intel(R) Atom(TM) CPU C3758 @ 2.20GHz


[Test Setup]
Steps to reproduce
1. Use the following command to build DPDK: 
CC=gcc meson -Denable_kmods=True -Dlibdir=lib --default-library=static
x86_64-native-linuxapp-gcc/ 
ninja -C x86_64-native-linuxapp-gcc/ 

2. Execute the following command in the dpdk directory.  
meson test -C x86_64-native-bsdapp-gcc/ seqlock_autotest

[Show the output from the previous commands]
2/2 DPDK:fast-tests / seqlock_autotest      FAIL             2.51s   (exit
status 255 or signal 127 SIGinvalid)
04:23:38 MALLOC_PERTURB_=139 DPDK_TEST=seqlock_autotest
/root/dpdk/x86_64-native-linuxapp-gcc/app/test/dpdk-test
--file-prefix=seqlock_autotest
----------------------------------- output -----------------------------------
stdout:
RTE>>seqlock_autotest^M
Reader observed inconsistent data values 10856068477537484964
9973142773974991064 9973142773974991064
Test Failed
RTE>>
stderr:
EAL: Detected CPU lcores: 8
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/seqlock_autotest/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: 1024 hugepages of size 2097152 reserved, but no mounted hugetlbfs found
for that size
APP: HPET is not enabled, using TSC as default timer

[Expected Result]
Test ok.

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