From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1023] [dpdk-22.07][meson test] perf-tests/ipsec_perf_autotest: Failed to test
Date: Wed, 01 Jun 2022 08:48:13 +0000 [thread overview]
Message-ID: <bug-1023-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=1023
Bug ID: 1023
Summary: [dpdk-22.07][meson test]
perf-tests/ipsec_perf_autotest: Failed to test
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: meson
Assignee: dev@dpdk.org
Reporter: yux.jiang@intel.com
Target Milestone: ---
Environment
DPDK version: Use make showversion or for a non-released version: git remote -v
&& git show-ref --heads
dpdk-22.07-rc0:60018ef app/acl: support different formats for IPv6 address
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.
DPDK_TEST=ipsec_perf_autotest MALLOC_PERTURB_=23
/root/dpdk/x86_64-native-linuxapp-gcc/app/test/dpdk-test -c 0xff --no-pci
Show the output from the previous commands.
root@bdw-de-226:~/dpdk# DPDK_TEST=ipsec_perf_autotest MALLOC_PERTURB_=23
/root/dpdk/x86_64-native-linuxapp-gcc/app/test/dpdk-test -c 0xff --no-pci
EAL: Detected CPU lcores: 16
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: VFIO support initialized
APP: HPET is not enabled, using TSC as default timer
RTE>>ipsec_perf_autotest
USER1: rte_ipsec_pkt_crypto_prepare fail
Test Failed
Expected Result:
Test OK
Regression
Is this issue a regression: (Y/N) N
First run it by using "meson test"
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-06-01 8:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 8:48 bugzilla [this message]
2022-06-24 7:47 ` bugzilla
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-1023-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).