All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1002] [meson test] Debug-tests/dump_* all meson test time out because commands are not registered to command list
Date: Wed, 27 Apr 2022 06:01:22 +0000	[thread overview]
Message-ID: <bug-1002-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 1002
           Summary: [meson test] Debug-tests/dump_* all meson test time
                    out because commands are not registered to command
                    list
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: meson
          Assignee: dev@dpdk.org
          Reporter: weiyuanx.li@intel.com
  Target Milestone: ---

[Environment]
DPDK version: Use make show version or for a non-released version: git remote
-v && git show-ref --heads
 22.07.0-rc0  55ae8965bf8eecd5ebec36663bb0f36018abf64b
OS: Red Hat Enterprise Linux 8.4 (Ootpa)/4.18.0-305.19.1.el8_4.x86_64
Compiler: gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-4)
Hardware platform: Intel(R) Xeon(R) Gold 6252N CPU @ 2.30GHz

[Test Setup]
Steps to reproduce
List the steps to reproduce the issue.

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-linuxapp-gcc dump_struct_sizes

[show the output]
root@localhost dpdk]# meson test -C x86_64-native-linuxapp-gcc
dump_struct_sizes
ninja: Entering directory `/root/dpdk/x86_64-native-linuxapp-gcc'
ninja: no work to do.
1/1 DPDK:debug-tests / dump_struct_sizes        TIMEOUT        600.02s   killed
by signal 15 SIGTERM
>>> MALLOC_PERTURB_=155 DPDK_TEST=dump_struct_sizes
>>> /root/dpdk/x86_64-native-linuxapp-gcc/app/test/dpdk-test



Ok:                 0
Expected Fail:      0
Fail:               0
Unexpected Pass:    0
Skipped:            0
Timeout:            1

Full log written to
/root/dpdk/x86_64-native-linuxapp-gcc/meson-logs/testlog.txt


show log from the testlog.txt.

1/1 DPDK:debug-tests / dump_struct_sizes TIMEOUT        600.02s   killed by
signal 15 SIGTERM
05:28:14 MALLOC_PERTURB_=155 DPDK_TEST=dump_struct_sizes
/root/dpdk/x86_64-native-linuxapp-gcc/app/test/dpdk-test
----------------------------------- output -----------------------------------
stdout:
RTE>>
stderr:
EAL: Detected CPU lcores: 96
EAL: Detected NUMA nodes: 2
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/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
APP: Invalid DPDK_TEST value 'dump_struct_sizes'
------------------------------------------------------------------------------


[Expected Result]
Test ok.

[Affected Test cases]
DPDK:debug-tests / dump_struct_sizes
DPDK:debug-tests / dump_mempool
DPDK:debug-tests / dump_malloc_stats
DPDK:debug-tests / dump_devargs
DPDK:debug-tests / dump_log_types
DPDK:debug-tests / dump_ring
DPDK:debug-tests / dump_physmem
DPDK:debug-tests / dump_memzone

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

                 reply	other threads:[~2022-04-27  6:01 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-1002-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.