From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Radu Nicolau <radu.nicolau@intel.com>
Subject: |FAILURE| pw154367 [PATCH] crypto/qat: fix out-of-place chain/cipher
Date: Thu, 12 Jun 2025 06:02:01 -0700 (PDT) [thread overview]
Message-ID: <684acfc9.170a0220.329865.39aeSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250612101414.240641-1-radu.nicolau@intel.com>
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/154367
_Testing issues_
Submitter: Radu Nicolau <radu.nicolau@intel.com>
Date: Thursday, June 12 2025 10:14:14
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:de7d4a7a657b22a366caa2e14723cd03d40bdb7c
154367 --> testing issues
Upstream job id: Generic-Unit-Test-DPDK#345351
Test environment and result as below:
+-------------------------------+----------------+
| Environment | dpdk_unit_test |
+===============================+================+
| CentOS Stream 10 | PASS |
+-------------------------------+----------------+
| CentOS Stream 9 | PASS |
+-------------------------------+----------------+
| Debian GNU/Linux 12 | PASS |
+-------------------------------+----------------+
| Fedora 40 (Clang) | PASS |
+-------------------------------+----------------+
| Fedora 40 | PASS |
+-------------------------------+----------------+
| Fedora 41 | PASS |
+-------------------------------+----------------+
| Fedora 41 (Clang) | PASS |
+-------------------------------+----------------+
| Red Hat Enterprise Linux 8.10 | PASS |
+-------------------------------+----------------+
| Ubuntu 22.04 | PASS |
+-------------------------------+----------------+
| Red Hat Enterprise Linux 9.5 | PASS |
+-------------------------------+----------------+
| Ubuntu 20.04 | PASS |
+-------------------------------+----------------+
| Ubuntu 24.04 | FAIL |
+-------------------------------+----------------+
==== Unit test summary for Ubuntu 24.04 (dpdk_unit_test): ====
ninja: Entering directory `/root/workspace/Generic-Unit-Test-DPDK/dpdk/build'
ninja: no work to do.
1/120 DPDK:fast-tests / acl_autotest OK 2.43s
2/120 DPDK:fast-tests / alarm_autotest OK 1.18s
3/120 DPDK:fast-tests / argparse_autotest OK 0.18s
4/120 DPDK:fast-tests / atomic_autotest OK 0.36s
5/120 DPDK:fast-tests / bitcount_autotest OK 0.19s
6/120 DPDK:fast-tests / bitmap_autotest OK 0.18s
7/120 DPDK:fast-tests / bitops_autotest OK 1.68s
8/120 DPDK:fast-tests / bitratestats_autotest OK 0.19s
9/120 DPDK:fast-tests / bitset_autotest OK 1.29s
10/120 DPDK:fast-tests / bpf_autotest OK 0.19s
11/120 DPDK:fast-tests / bpf_convert_autotest OK 0.19s
12/120 DPDK:fast-tests / byteorder_autotest OK 0.18s
13/120 DPDK:fast-tests / cfgfile_autotest OK 0.18s
14/120 DPDK:fast-tests / cksum_autotest OK 0.19s
15/120 DPDK:fast-tests / cmdline_autotest OK 0.18s
16/120 DPDK:fast-tests / common_autotest OK 0.53s
17/120 DPDK:fast-tests / compressdev_autotest SKIP 0.15s exit status 77
18/120 DPDK:fast-tests / cpuflags_autotest OK 0.19s
19/120 DPDK:fast-tests / crc_autotest OK 0.18s
20/120 DPDK:fast-tests / user_delay_us OK 0.18s
21/120 DPDK:fast-tests / debug_autotest OK 0.41s
22/120 DPDK:fast-tests / devargs_autotest OK 0.19s
23/120 DPDK:fast-tests / dispatcher_autotest SKIP 0.16s exit status 77
24/120 DPDK:fast-tests / distributor_autotest OK 0.85s
25/120 DPDK:fast-tests / eal_flags_c_opt_autotest OK 1.01s
26/120 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.36s
27/120 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.52s
28/120 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.23s
29/120 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.55s
30/120 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.45s
31/120 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.38s
32/120 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.61s
33/120 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.31s
34/120 DPDK:fast-tests / eal_flags_mem_autotest OK 0.82s
35/120 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 2.20s
36/120 DPDK:fast-tests / eal_flags_misc_autotest OK 2.31s
37/120 DPDK:fast-tests / eal_fs_autotest OK 0.19s
38/120 DPDK:fast-tests / errno_autotest OK 0.18s
39/120 DPDK:fast-tests / ethdev_link_status OK 0.18s
40/120 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 0.47s
41/120 DPDK:fast-tests / event_ring_autotest OK 0.19s
42/120 DPDK:fast-tests / event_vector_adapter_autotest FAIL 2.26s (exit status 255 or signal 127 SIGinvalid)
>>> DPDK_TEST=event_vector_adapter_autotest MALLOC_PERTURB_=73 /root/workspace/Generic-Unit-Test-DPDK/dpdk/build/app/dpdk-test --no-huge -m 2048
43/120 DPDK:fast-tests / eventdev_common_autotest OK 0.19s
44/120 DPDK:fast-tests / eventdev_selftest_sw OK 0.22s
45/120 DPDK:fast-tests / fbarray_autotest OK 0.18s
46/120 DPDK:fast-tests / fib_autotest OK 0.74s
47/120 DPDK:fast-tests / fib6_autotest OK 0.64s
48/120 DPDK:fast-tests / func_reentrancy_autotest OK 0.53s
49/120 DPDK:fast-tests / graph_autotest OK 0.19s
50/120 DPDK:fast-tests / node_list_dump OK 0.18s
51/120 DPDK:fast-tests / hash_autotest OK 0.30s
52/120 DPDK:fast-tests / hash_readwrite_func_autotest SKIP 0.16s exit status 77
53/120 DPDK:fast-tests / interrupt_autotest OK 1.21s
54/120 DPDK:fast-tests / ipfrag_autotest OK 0.16s
55/120 DPDK:fast-tests / ipsec_autotest SKIP 0.19s exit status 77
56/120 DPDK:fast-tests / kvargs_autotest OK 0.19s
57/120 DPDK:fast-tests / latencystats_autotest OK 0.19s
58/120 DPDK:fast-tests / lcore_var_autotest OK 0.33s
59/120 DPDK:fast-tests / lcores_autotest OK 0.71s
60/120 DPDK:fast-tests / logs_autotest OK 0.18s
61/120 DPDK:fast-tests / lpm_autotest OK 1.48s
62/120 DPDK:fast-tests / lpm6_autotest OK 2.69s
63/120 DPDK:fast-tests / malloc_autotest OK 0.39s
64/120 DPDK:fast-tests / mbuf_autotest OK 0.18s
65/120 DPDK:fast-tests / mcslock_autotest OK 0.43s
66/120 DPDK:fast-tests / member_autotest OK 0.77s
67/120 DPDK:fast-tests / memcpy_autotest OK 1.70s
68/120 DPDK:fast-tests / memory_autotest OK 0.15s
69/120 DPDK:fast-tests / mempool_autotest OK 0.45s
70/120 DPDK:fast-tests / memzone_autotest OK 0.16s
71/120 DPDK:fast-tests / meter_autotest OK 0.20s
72/120 DPDK:fast-tests / metrics_autotest OK 0.20s
73/120 DPDK:fast-tests / multiprocess_autotest OK 0.32s
74/120 DPDK:fast-tests / net_ether_autotest OK 0.50s
75/120 DPDK:fast-tests / net_ipv6_autotest OK 0.20s
76/120 DPDK:fast-tests / pcapng_autotest OK 5.82s
77/120 DPDK:fast-tests / pdcp_autotest SKIP 0.15s exit status 77
78/120 DPDK:fast-tests / pdump_autotest OK 0.35s
79/120 DPDK:fast-tests / per_lcore_autotest OK 0.29s
80/120 DPDK:fast-tests / pflock_autotest OK 0.29s
81/120 DPDK:fast-tests / pie_autotest OK 0.19s
82/120 DPDK:fast-tests / ring_pmd_autotest OK 0.19s
83/120 DPDK:fast-tests / power_autotest OK 0.18s
84/120 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.16s exit status 77
85/120 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.20s exit status 77
86/120 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.15s exit status 77
87/120 DPDK:fast-tests / prefetch_autotest OK 0.20s
88/120 DPDK:fast-tests / ptr_compress_autotest OK 0.19s
89/120 DPDK:fast-tests / rawdev_autotest OK 0.19s
90/120 DPDK:fast-tests / rcu_qsbr_autotest OK 0.29s
91/120 DPDK:fast-tests / reorder_autotest OK 0.32s
92/120 DPDK:fast-tests / rib_autotest OK 3.49s
93/120 DPDK:fast-tests / rib6_autotest OK 3.51s
94/120 DPDK:fast-tests / ring_autotest OK 0.19s
95/120 DPDK:fast-tests / rwlock_test1_autotest OK 0.29s
96/120 DPDK:fast-tests / rwlock_rda_autotest OK 5.20s
97/120 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.18s
98/120 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.20s
99/120 DPDK:fast-tests / sched_autotest OK 0.19s
100/120 DPDK:fast-tests / security_autotest OK 0.15s
101/120 DPDK:fast-tests / seqlock_autotest SKIP 0.19s exit status 77
102/120 DPDK:fast-tests / service_autotest OK 0.28s
103/120 DPDK:fast-tests / soring_autotest OK 0.19s
104/120 DPDK:fast-tests / spinlock_autotest OK 0.19s
105/120 DPDK:fast-tests / stack_autotest OK 0.19s
106/120 DPDK:fast-tests / stack_lf_autotest OK 0.25s
107/120 DPDK:fast-tests / string_autotest OK 0.19s
108/120 DPDK:fast-tests / table_autotest OK 4.69s
109/120 DPDK:fast-tests / tailq_autotest OK 0.18s
110/120 DPDK:fast-tests / telemetry_data_autotest OK 0.19s
111/120 DPDK:fast-tests / telemetry_json_autotest OK 0.19s
112/120 DPDK:fast-tests / thash_autotest OK 0.20s
113/120 DPDK:fast-tests / threads_autotest OK 0.35s
114/120 DPDK:fast-tests / ticketlock_autotest OK 0.20s
115/120 DPDK:fast-tests / timer_autotest OK 2.50s
116/120 DPDK:fast-tests / trace_autotest OK 0.20s
117/120 DPDK:fast-tests / trace_autotest_with_traces OK 0.20s
118/120 DPDK:fast-tests / vdev_autotest OK 0.18s
119/120 DPDK:fast-tests / version_autotest OK 0.18s
120/120 DPDK:fast-tests / telemetry_all OK 1.05s
Ok: 110
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 9
Timeout: 0
Full log written to /root/workspace/Generic-Unit-Test-DPDK/dpdk/build/meson-logs/testlog.txt
Test log output from the failed test event_vector_adapter_autotest:
Sorry, we were not able to find the logs for this test.
Download the log output from the CI site for this test run.
==== End log output ====
CentOS Stream 10
Kernel: Depends on container host
Compiler: gcc 14.2.1 20241104 (Red Hat 14.2.1-6)
CentOS Stream 9
Kernel: Depends on container host
Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)
Debian GNU/Linux 12
Kernel: 5.15
Compiler: gcc gcc (Debian 12.2.0-14) 12.2.0
Fedora 40 (Clang)
Kernel: Depends on container host
Compiler: clang 18.1.8 (Fedora 18.1.8-1.fc40)
Fedora 40
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)
Fedora 41
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)
Fedora 41 (Clang)
Kernel: Depends on container host
Compiler: clang 19.1.5 (Fedora 19.1.5-1.fc41)
Red Hat Enterprise Linux 8.10
Kernel: 5.15
Compiler: gcc gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-22)
Ubuntu 22.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Red Hat Enterprise Linux 9.5
Kernel: 5.15
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-2)
Ubuntu 20.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Ubuntu 24.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33395/
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:[~2025-06-12 13:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250612101414.240641-1-radu.nicolau@intel.com>
2025-06-12 9:39 ` |SUCCESS| pw154367 [PATCH] crypto/qat: fix out-of-place chain/cipher/auth headers qemudev
2025-06-12 9:43 ` qemudev
2025-06-12 10:14 ` checkpatch
2025-06-12 11:39 ` 0-day Robot
2025-06-12 11:56 ` |SUCCESS| pw154367 [PATCH] crypto/qat: fix out-of-place chain/cipher dpdklab
2025-06-12 11:58 ` dpdklab
2025-06-12 12:01 ` dpdklab
2025-06-12 12:02 ` |PENDING| " dpdklab
2025-06-12 12:12 ` |SUCCESS| " dpdklab
2025-06-12 12:23 ` dpdklab
2025-06-12 12:24 ` |PENDING| " dpdklab
2025-06-12 12:29 ` |SUCCESS| " dpdklab
2025-06-12 12:43 ` |WARNING| " dpdklab
2025-06-12 12:43 ` dpdklab
2025-06-12 12:54 ` |FAILURE| " dpdklab
2025-06-12 13:01 ` |PENDING| " dpdklab
2025-06-12 13:02 ` dpdklab [this message]
2025-06-12 13:08 ` |SUCCESS| " dpdklab
2025-06-12 13:15 ` |PENDING| " dpdklab
2025-06-12 14:03 ` |WARNING| " dpdklab
2025-06-12 14:22 ` |SUCCESS| " dpdklab
2025-06-12 17:02 ` dpdklab
2025-06-12 23:51 ` 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=684acfc9.170a0220.329865.39aeSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=radu.nicolau@intel.com \
--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).