From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Mattias Ronnblom <mattias.ronnblom@ericsson.com>
Subject: |FAILURE| pw154825-154824 [PATCH] [RFC,4/4] event/dsw: implement enq
Date: Sun, 29 Jun 2025 13:13:39 -0700 (PDT) [thread overview]
Message-ID: <68619e73.050a0220.85e0b.afa2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250629165214.3468-5-mattias.ronnblom@ericsson.com>
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/154824
_Testing issues_
Submitter: Mattias Ronnblom <mattias.ronnblom@ericsson.com>
Date: Sunday, June 29 2025 16:52:14
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:ff1c2b2f81dba565a5eed8576ca4a7e956fe3886
154825-154824 --> testing issues
Upstream job id: Generic-VM-Unit-Test-DPDK#29569
Test environment and result as below:
+-------------------------------+----------------+
| Environment | dpdk_unit_test |
+===============================+================+
| Fedora Linux 40 | PASS |
+-------------------------------+----------------+
| CentOS Stream 9 | PASS |
+-------------------------------+----------------+
| CentOS Stream 10 | PASS |
+-------------------------------+----------------+
| Debian GNU/Linux 12 | PASS |
+-------------------------------+----------------+
| Fedora Linux 41 | FAIL |
+-------------------------------+----------------+
| Red Hat Enterprise Linux 8.10 | PASS |
+-------------------------------+----------------+
| Red Hat Enterprise Linux 9.5 | PASS |
+-------------------------------+----------------+
| Ubuntu 20.04 | PASS |
+-------------------------------+----------------+
| Ubuntu 22.04 | PASS |
+-------------------------------+----------------+
| Ubuntu 24.04 | PASS |
+-------------------------------+----------------+
| Windows Server 2022 | PASS |
+-------------------------------+----------------+
==== Unit test summary for Fedora Linux 41 (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 4.01s
2/120 DPDK:fast-tests / alarm_autotest OK 1.28s
3/120 DPDK:fast-tests / argparse_autotest OK 0.29s
4/120 DPDK:fast-tests / atomic_autotest OK 0.46s
5/120 DPDK:fast-tests / bitcount_autotest OK 0.30s
6/120 DPDK:fast-tests / bitmap_autotest OK 0.17s
7/120 DPDK:fast-tests / bitops_autotest OK 2.07s
8/120 DPDK:fast-tests / bitratestats_autotest OK 0.31s
9/120 DPDK:fast-tests / bitset_autotest OK 2.49s
10/120 DPDK:fast-tests / bpf_autotest OK 0.27s
11/120 DPDK:fast-tests / bpf_convert_autotest OK 0.29s
12/120 DPDK:fast-tests / byteorder_autotest OK 0.17s
13/120 DPDK:fast-tests / cfgfile_autotest OK 0.29s
14/120 DPDK:fast-tests / cksum_autotest OK 0.27s
15/120 DPDK:fast-tests / cmdline_autotest OK 0.23s
16/120 DPDK:fast-tests / common_autotest OK 0.71s
17/120 DPDK:fast-tests / compressdev_autotest SKIP 0.32s exit status 77
18/120 DPDK:fast-tests / cpuflags_autotest OK 0.17s
19/120 DPDK:fast-tests / crc_autotest OK 0.18s
20/120 DPDK:fast-tests / user_delay_us OK 0.29s
21/120 DPDK:fast-tests / debug_autotest OK 0.67s
22/120 DPDK:fast-tests / devargs_autotest OK 0.29s
23/120 DPDK:fast-tests / dispatcher_autotest SKIP 0.14s exit status 77
24/120 DPDK:fast-tests / distributor_autotest OK 1.60s
25/120 DPDK:fast-tests / eal_flags_c_opt_autotest OK 1.23s
26/120 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.31s
27/120 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.67s
28/120 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.34s
29/120 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.54s
30/120 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.61s
31/120 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.51s
32/120 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.78s
33/120 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.29s
34/120 DPDK:fast-tests / eal_flags_mem_autotest OK 1.03s
35/120 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 2.73s
36/120 DPDK:fast-tests / eal_flags_misc_autotest FAIL 1.18s (exit status 255 or signal 127 SIGinvalid)
>>> MALLOC_PERTURB_=21 DPDK_TEST=eal_flags_misc_autotest /root/workspace/Generic-Unit-Test-DPDK/dpdk/build/app/dpdk-test
37/120 DPDK:fast-tests / eal_fs_autotest OK 0.22s
38/120 DPDK:fast-tests / errno_autotest OK 0.17s
39/120 DPDK:fast-tests / ethdev_link_status OK 0.29s
40/120 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 0.71s
41/120 DPDK:fast-tests / event_ring_autotest OK 0.20s
42/120 DPDK:fast-tests / eventdev_common_autotest OK 0.28s
43/120 DPDK:fast-tests / eventdev_selftest_sw OK 0.35s
44/120 DPDK:fast-tests / fbarray_autotest OK 0.17s
45/120 DPDK:fast-tests / fib_autotest OK 1.26s
46/120 DPDK:fast-tests / fib6_autotest OK 1.21s
47/120 DPDK:fast-tests / func_reentrancy_autotest OK 0.95s
48/120 DPDK:fast-tests / graph_autotest OK 0.31s
49/120 DPDK:fast-tests / node_list_dump OK 0.30s
50/120 DPDK:fast-tests / graph_feature_arc_autotest OK 0.25s
51/120 DPDK:fast-tests / hash_autotest OK 0.42s
52/120 DPDK:fast-tests / hash_readwrite_func_autotest SKIP 0.21s exit status 77
53/120 DPDK:fast-tests / interrupt_autotest OK 1.74s
54/120 DPDK:fast-tests / ipfrag_autotest OK 0.14s
55/120 DPDK:fast-tests / ipsec_autotest SKIP 0.27s exit status 77
56/120 DPDK:fast-tests / kvargs_autotest OK 0.27s
57/120 DPDK:fast-tests / latencystats_autotest OK 0.34s
58/120 DPDK:fast-tests / lcore_var_autotest OK 0.50s
59/120 DPDK:fast-tests / lcores_autotest OK 1.24s
60/120 DPDK:fast-tests / logs_autotest OK 0.26s
61/120 DPDK:fast-tests / lpm_autotest OK 2.36s
62/120 DPDK:fast-tests / lpm6_autotest OK 5.05s
63/120 DPDK:fast-tests / malloc_autotest OK 0.67s
64/120 DPDK:fast-tests / mbuf_autotest OK 0.37s
65/120 DPDK:fast-tests / mcslock_autotest OK 0.64s
66/120 DPDK:fast-tests / member_autotest OK 1.79s
67/120 DPDK:fast-tests / memcpy_autotest OK 3.91s
68/120 DPDK:fast-tests / memory_autotest OK 0.21s
69/120 DPDK:fast-tests / mempool_autotest OK 0.52s
70/120 DPDK:fast-tests / memzone_autotest OK 0.25s
71/120 DPDK:fast-tests / meter_autotest OK 0.30s
72/120 DPDK:fast-tests / metrics_autotest OK 0.30s
73/120 DPDK:fast-tests / multiprocess_autotest OK 0.51s
74/120 DPDK:fast-tests / net_ether_autotest OK 0.80s
75/120 DPDK:fast-tests / net_ipv6_autotest OK 0.26s
76/120 DPDK:fast-tests / pcapng_autotest OK 11.76s
77/120 DPDK:fast-tests / pdcp_autotest SKIP 0.18s exit status 77
78/120 DPDK:fast-tests / pdump_autotest OK 0.50s
79/120 DPDK:fast-tests / per_lcore_autotest OK 0.44s
80/120 DPDK:fast-tests / pflock_autotest OK 0.47s
81/120 DPDK:fast-tests / pie_autotest OK 0.36s
82/120 DPDK:fast-tests / ring_pmd_autotest OK 0.30s
83/120 DPDK:fast-tests / power_autotest OK 0.29s
84/120 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.14s exit status 77
85/120 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.34s exit status 77
86/120 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.20s exit status 77
87/120 DPDK:fast-tests / prefetch_autotest OK 0.27s
88/120 DPDK:fast-tests / ptr_compress_autotest OK 0.30s
89/120 DPDK:fast-tests / rawdev_autotest OK 0.30s
90/120 DPDK:fast-tests / rcu_qsbr_autotest OK 0.47s
91/120 DPDK:fast-tests / reorder_autotest OK 0.39s
92/120 DPDK:fast-tests / rib_autotest OK 6.40s
93/120 DPDK:fast-tests / rib6_autotest OK 6.29s
94/120 DPDK:fast-tests / ring_autotest OK 0.27s
95/120 DPDK:fast-tests / rwlock_test1_autotest OK 0.47s
96/120 DPDK:fast-tests / rwlock_rda_autotest OK 5.27s
97/120 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.21s
98/120 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.18s
99/120 DPDK:fast-tests / sched_autotest OK 0.29s
100/120 DPDK:fast-tests / security_autotest OK 0.18s
101/120 DPDK:fast-tests / seqlock_autotest SKIP 0.18s exit status 77
102/120 DPDK:fast-tests / service_autotest OK 0.47s
103/120 DPDK:fast-tests / soring_autotest OK 0.31s
104/120 DPDK:fast-tests / spinlock_autotest OK 0.29s
105/120 DPDK:fast-tests / stack_autotest OK 0.18s
106/120 DPDK:fast-tests / stack_lf_autotest OK 0.39s
107/120 DPDK:fast-tests / string_autotest OK 0.27s
108/120 DPDK:fast-tests / table_autotest OK 7.50s
109/120 DPDK:fast-tests / tailq_autotest OK 0.17s
110/120 DPDK:fast-tests / telemetry_data_autotest OK 0.29s
111/120 DPDK:fast-tests / telemetry_json_autotest OK 0.30s
112/120 DPDK:fast-tests / thash_autotest OK 0.24s
113/120 DPDK:fast-tests / threads_autotest OK 0.87s
114/120 DPDK:fast-tests / ticketlock_autotest OK 0.30s
115/120 DPDK:fast-tests / timer_autotest OK 2.78s
116/120 DPDK:fast-tests / trace_autotest OK 0.46s
117/120 DPDK:fast-tests / trace_autotest_with_traces OK 0.18s
118/120 DPDK:fast-tests / vdev_autotest OK 0.30s
119/120 DPDK:fast-tests / version_autotest OK 0.17s
120/120 DPDK:fast-tests / telemetry_all SKIP 0.01s exit status 77
Ok: 109
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 10
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 eal_flags_misc_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 ====
Fedora Linux 40
Kernel: 5.15
Compiler: gcc gcc (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3)
CentOS Stream 9
Kernel: 5.15
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-7)
CentOS Stream 10
Kernel: 5.15
Compiler: gcc gcc (GCC) 14.2.1 20250110 (Red Hat 14.2.1-8)
Debian GNU/Linux 12
Kernel: 5.15
Compiler: gcc gcc (Debian 12.2.0-14+deb12u1) 12.2.0
Fedora Linux 41
Kernel: 5.15
Compiler: clang gcc (GCC) 14.3.1 20250523 (Red Hat 14.3.1-1)
Red Hat Enterprise Linux 8.10
Kernel: 5.15
Compiler: gcc gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-22)
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 22.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Ubuntu 24.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33533/
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-29 20:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250629165214.3468-5-mattias.ronnblom@ericsson.com>
2025-06-29 16:33 ` |SUCCESS| pw154825-154824 [RFC 4/4] event/dsw: implement enqueue optimized for prealloced events qemudev
2025-06-29 16:38 ` qemudev
2025-06-29 17:08 ` |SUCCESS| pw154824 " checkpatch
2025-06-29 18:02 ` |FAILURE| " 0-day Robot
2025-06-29 18:39 ` |SUCCESS| pw154825-154824 [PATCH] [RFC,4/4] event/dsw: implement enq dpdklab
2025-06-29 18:39 ` dpdklab
2025-06-29 18:43 ` dpdklab
2025-06-29 19:02 ` dpdklab
2025-06-29 19:03 ` dpdklab
2025-06-29 19:07 ` |PENDING| " dpdklab
2025-06-29 19:13 ` |SUCCESS| " dpdklab
2025-06-29 19:15 ` |PENDING| " dpdklab
2025-06-29 19:19 ` dpdklab
2025-06-29 19:24 ` dpdklab
2025-06-29 19:44 ` |FAILURE| " dpdklab
2025-06-29 19:44 ` dpdklab
2025-06-29 19:52 ` dpdklab
2025-06-29 20:13 ` dpdklab [this message]
2025-06-29 20:38 ` dpdklab
2025-06-29 20:41 ` dpdklab
2025-06-29 20:49 ` |WARNING| " dpdklab
2025-06-29 21:12 ` |SUCCESS| " dpdklab
2025-06-29 23:21 ` dpdklab
2025-06-30 2:08 ` dpdklab
2025-06-30 2:09 ` 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=68619e73.050a0220.85e0b.afa2SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=mattias.ronnblom@ericsson.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).