From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Chaoyong He <chaoyong.he@corigine.com>
Subject: |FAILURE| pw138145 [PATCH] examples/ipsec-secgw: fix Rx queue ID in
Date: Mon, 11 Mar 2024 01:32:49 -0700 (PDT) [thread overview]
Message-ID: <65eec1b1.b00a0220.2a05a.4008SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240311023247.2520028-1-chaoyong.he@corigine.com>
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/138145
_Testing issues_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Monday, March 11 2024 02:32:47
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a86f381b826660e88794754c41d3aec79ce9b87c
138145 --> testing fail
Test environment and result as below:
+------------------+----------------+
| Environment | dpdk_unit_test |
+==================+================+
| CentOS Stream 8 | PASS |
+------------------+----------------+
| Debian Bullseye | PASS |
+------------------+----------------+
| Debian 12 (arm) | FAIL |
+------------------+----------------+
| CentOS Stream 9 | PASS |
+------------------+----------------+
| Fedora 38 | PASS |
+------------------+----------------+
| RHEL8 | PASS |
+------------------+----------------+
| Ubuntu 22.04 | PASS |
+------------------+----------------+
| Ubuntu 20.04 | PASS |
+------------------+----------------+
| openSUSE Leap 15 | PASS |
+------------------+----------------+
| Fedora 37 | PASS |
+------------------+----------------+
==== 20 line log output for Debian 12 (arm) (dpdk_unit_test): ====
Installing symlink pointing to librte_event_opdl.so.24 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_event_opdl.so
Installing symlink pointing to librte_event_skeleton.so.24.1 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_event_skeleton.so.24
Installing symlink pointing to librte_event_skeleton.so.24 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_event_skeleton.so
Installing symlink pointing to librte_event_sw.so.24.1 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_event_sw.so.24
Installing symlink pointing to librte_event_sw.so.24 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_event_sw.so
Installing symlink pointing to librte_event_octeontx.so.24.1 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_event_octeontx.so.24
Installing symlink pointing to librte_event_octeontx.so.24 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_event_octeontx.so
Installing symlink pointing to librte_baseband_acc.so.24.1 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_baseband_acc.so.24
Installing symlink pointing to librte_baseband_acc.so.24 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_baseband_acc.so
Installing symlink pointing to librte_baseband_fpga_5gnr_fec.so.24.1 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_baseband_fpga_5gnr_fec.so.24
Installing symlink pointing to librte_baseband_fpga_5gnr_fec.so.24 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_baseband_fpga_5gnr_fec.so
Installing symlink pointing to librte_baseband_fpga_lte_fec.so.24.1 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_baseband_fpga_lte_fec.so.24
Installing symlink pointing to librte_baseband_fpga_lte_fec.so.24 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_baseband_fpga_lte_fec.so
Installing symlink pointing to librte_baseband_la12xx.so.24.1 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_baseband_la12xx.so.24
Installing symlink pointing to librte_baseband_la12xx.so.24 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_baseband_la12xx.so
Installing symlink pointing to librte_baseband_null.so.24.1 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_baseband_null.so.24
Installing symlink pointing to librte_baseband_null.so.24 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_baseband_null.so
Installing symlink pointing to librte_baseband_turbo_sw.so.24.1 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_baseband_turbo_sw.so.24
Installing symlink pointing to librte_baseband_turbo_sw.so.24 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_baseband_turbo_sw.so
Running custom install script '/bin/sh /home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/config/../buildtools/symlink-drivers-solibs.sh lib/x86_64-linux-gnu dpdk/pmds-24.1'
==== End log output ====
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 11
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29493/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-03-11 8:32 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240311023247.2520028-1-chaoyong.he@corigine.com>
2024-03-11 2:10 ` |SUCCESS| pw138145 [PATCH] examples/ipsec-secgw: fix Rx queue ID in Rx callback qemudev
2024-03-11 2:14 ` qemudev
2024-03-11 2:34 ` checkpatch
2024-03-11 3:22 ` 0-day Robot
2024-03-11 7:32 ` |SUCCESS| pw138145 [PATCH] examples/ipsec-secgw: fix Rx queue ID in dpdklab
2024-03-11 7:46 ` dpdklab
2024-03-11 7:47 ` dpdklab
2024-03-11 7:48 ` dpdklab
2024-03-11 7:49 ` dpdklab
2024-03-11 7:50 ` dpdklab
2024-03-11 8:01 ` dpdklab
2024-03-11 8:02 ` dpdklab
2024-03-11 8:02 ` dpdklab
2024-03-11 8:03 ` dpdklab
2024-03-11 8:04 ` dpdklab
2024-03-11 8:04 ` dpdklab
2024-03-11 8:09 ` dpdklab
2024-03-11 8:10 ` dpdklab
2024-03-11 8:14 ` dpdklab
2024-03-11 8:16 ` dpdklab
2024-03-11 8:16 ` dpdklab
2024-03-11 8:17 ` dpdklab
2024-03-11 8:19 ` dpdklab
2024-03-11 8:19 ` dpdklab
2024-03-11 8:20 ` dpdklab
2024-03-11 8:21 ` dpdklab
2024-03-11 8:21 ` dpdklab
2024-03-11 8:21 ` dpdklab
2024-03-11 8:22 ` dpdklab
2024-03-11 8:22 ` dpdklab
2024-03-11 8:23 ` dpdklab
2024-03-11 8:23 ` dpdklab
2024-03-11 8:23 ` dpdklab
2024-03-11 8:23 ` dpdklab
2024-03-11 8:24 ` dpdklab
2024-03-11 8:24 ` dpdklab
2024-03-11 8:24 ` dpdklab
2024-03-11 8:25 ` dpdklab
2024-03-11 8:26 ` dpdklab
2024-03-11 8:26 ` dpdklab
2024-03-11 8:26 ` |FAILURE| " dpdklab
2024-03-11 8:27 ` |SUCCESS| " dpdklab
2024-03-11 8:27 ` dpdklab
2024-03-11 8:28 ` dpdklab
2024-03-11 8:28 ` |FAILURE| " dpdklab
2024-03-11 8:28 ` |SUCCESS| " dpdklab
2024-03-11 8:28 ` |FAILURE| " dpdklab
2024-03-11 8:29 ` dpdklab
2024-03-11 8:29 ` |SUCCESS| " dpdklab
2024-03-11 8:30 ` dpdklab
2024-03-11 8:30 ` |FAILURE| " dpdklab
2024-03-11 8:30 ` dpdklab
2024-03-11 8:31 ` dpdklab
2024-03-11 8:31 ` |SUCCESS| " dpdklab
2024-03-11 8:31 ` dpdklab
2024-03-11 8:31 ` dpdklab
2024-03-11 8:32 ` dpdklab
2024-03-11 8:32 ` dpdklab
2024-03-11 8:32 ` dpdklab
2024-03-11 8:32 ` dpdklab [this message]
2024-03-11 8:33 ` |FAILURE| " dpdklab
2024-03-11 8:33 ` dpdklab
2024-03-11 8:33 ` dpdklab
2024-03-11 8:33 ` |SUCCESS| " dpdklab
2024-03-11 8:34 ` dpdklab
2024-03-11 8:34 ` dpdklab
2024-03-11 8:34 ` dpdklab
2024-03-11 8:34 ` dpdklab
2024-03-11 8:34 ` dpdklab
2024-03-11 8:37 ` dpdklab
2024-03-11 8:41 ` dpdklab
2024-03-11 8:43 ` |FAILURE| " dpdklab
2024-03-11 8:44 ` |SUCCESS| " dpdklab
2024-03-11 8:52 ` dpdklab
2024-03-11 9:01 ` dpdklab
2024-03-11 9:25 ` dpdklab
2024-03-14 19:29 ` dpdklab
2024-03-14 20:16 ` dpdklab
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=65eec1b1.b00a0220.2a05a.4008SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=chaoyong.he@corigine.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@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).