From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Gagandeep Singh <g.singh@nxp.com>
Subject: |FAILURE| pw154953-154957 [PATCH] [v8,5/5] net/dpaa2: enable softwar
Date: Wed, 02 Jul 2025 11:55:36 -0700 (PDT) [thread overview]
Message-ID: <686580a8.170a0220.11eb9a.0e4fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250702095144.3087250-6-g.singh@nxp.com>
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/154957
_Testing issues_
Submitter: Gagandeep Singh <g.singh@nxp.com>
Date: Wednesday, July 02 2025 09:51:44
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:b18c543ec30729ccc7708a6e064a1f9db5d8c11f
154953-154957 --> testing issues
Upstream job id: Generic-Unit-Test-DPDK#351828
Test environment and result as below:
+-------------------------------+----------------+
| Environment | dpdk_unit_test |
+===============================+================+
| CentOS Stream 10 | PASS |
+-------------------------------+----------------+
| Debian GNU/Linux 12 | PASS |
+-------------------------------+----------------+
| Red Hat Enterprise Linux 9.5 | PASS |
+-------------------------------+----------------+
| CentOS Stream 9 | PASS |
+-------------------------------+----------------+
| Fedora Linux 40 | PASS |
+-------------------------------+----------------+
| Red Hat Enterprise Linux 8.10 | PASS |
+-------------------------------+----------------+
| Fedora Linux 41 | PEND |
+-------------------------------+----------------+
| Ubuntu 20.04 | PASS |
+-------------------------------+----------------+
| Ubuntu 24.04 | FAIL |
+-------------------------------+----------------+
| Ubuntu 22.04 | PASS |
+-------------------------------+----------------+
| Windows Server 2022 | PASS |
+-------------------------------+----------------+
==== 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/121 DPDK:fast-tests / acl_autotest OK 2.58s
2/121 DPDK:fast-tests / alarm_autotest OK 1.18s
3/121 DPDK:fast-tests / argparse_autotest OK 0.18s
4/121 DPDK:fast-tests / atomic_autotest OK 0.36s
5/121 DPDK:fast-tests / bitcount_autotest OK 0.19s
6/121 DPDK:fast-tests / bitmap_autotest OK 0.17s
7/121 DPDK:fast-tests / bitops_autotest OK 1.74s
8/121 DPDK:fast-tests / bitratestats_autotest OK 0.31s
9/121 DPDK:fast-tests / bitset_autotest OK 1.42s
10/121 DPDK:fast-tests / bpf_autotest OK 0.17s
11/121 DPDK:fast-tests / bpf_convert_autotest OK 0.18s
12/121 DPDK:fast-tests / byteorder_autotest OK 0.18s
13/121 DPDK:fast-tests / cfgfile_autotest OK 0.21s
14/121 DPDK:fast-tests / cksum_autotest OK 0.23s
15/121 DPDK:fast-tests / cmdline_autotest OK 0.19s
16/121 DPDK:fast-tests / common_autotest OK 0.56s
17/121 DPDK:fast-tests / compressdev_autotest SKIP 0.14s exit status 77
18/121 DPDK:fast-tests / cpuflags_autotest OK 0.17s
19/121 DPDK:fast-tests / crc_autotest OK 0.17s
20/121 DPDK:fast-tests / user_delay_us OK 0.17s
21/121 DPDK:fast-tests / debug_autotest OK 0.51s
22/121 DPDK:fast-tests / devargs_autotest OK 0.19s
23/121 DPDK:fast-tests / dispatcher_autotest SKIP 0.33s exit status 77
24/121 DPDK:fast-tests / distributor_autotest OK 1.23s
25/121 DPDK:fast-tests / eal_flags_c_opt_autotest OK 0.77s
26/121 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.29s
27/121 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.57s
28/121 DPDK:fast-tests / eal_flags_hpet_autotest OK 1.06s
29/121 DPDK:fast-tests / eal_flags_no_huge_autotest OK 1.02s
30/121 DPDK:fast-tests / eal_flags_a_opt_autotest OK 1.93s
31/121 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.93s
32/121 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 1.54s
33/121 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.83s
34/121 DPDK:fast-tests / eal_flags_mem_autotest OK 1.41s
35/121 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 5.71s
36/121 DPDK:fast-tests / eal_flags_misc_autotest OK 1.96s
37/121 DPDK:fast-tests / eal_fs_autotest OK 0.19s
38/121 DPDK:fast-tests / errno_autotest OK 0.17s
39/121 DPDK:fast-tests / ethdev_link_status OK 0.17s
40/121 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 0.46s
41/121 DPDK:fast-tests / event_ring_autotest OK 0.22s
42/121 DPDK:fast-tests / event_vector_adapter_autotest FAIL 1.58s (exit status 255 or signal 127 SIGinvalid)
>>> DPDK_TEST=event_vector_adapter_autotest MALLOC_PERTURB_=91 /root/workspace/Generic-Unit-Test-DPDK/dpdk/build/app/dpdk-test --no-huge -m 2048
43/121 DPDK:fast-tests / eventdev_common_autotest OK 0.23s
44/121 DPDK:fast-tests / eventdev_selftest_sw OK 0.21s
45/121 DPDK:fast-tests / fbarray_autotest OK 0.17s
46/121 DPDK:fast-tests / fib_autotest OK 1.07s
47/121 DPDK:fast-tests / fib6_autotest OK 1.31s
48/121 DPDK:fast-tests / func_reentrancy_autotest OK 1.30s
49/121 DPDK:fast-tests / graph_autotest OK 0.34s
50/121 DPDK:fast-tests / node_list_dump OK 0.23s
51/121 DPDK:fast-tests / graph_feature_arc_autotest OK 0.30s
52/121 DPDK:fast-tests / hash_autotest OK 0.57s
53/121 DPDK:fast-tests / hash_readwrite_func_autotest SKIP 0.23s exit status 77
54/121 DPDK:fast-tests / interrupt_autotest OK 1.34s
55/121 DPDK:fast-tests / ipfrag_autotest OK 0.23s
56/121 DPDK:fast-tests / ipsec_autotest SKIP 0.34s exit status 77
57/121 DPDK:fast-tests / kvargs_autotest OK 0.41s
58/121 DPDK:fast-tests / latencystats_autotest OK 0.29s
59/121 DPDK:fast-tests / lcore_var_autotest OK 0.66s
60/121 DPDK:fast-tests / lcores_autotest OK 1.94s
61/121 DPDK:fast-tests / logs_autotest OK 0.39s
62/121 DPDK:fast-tests / lpm_autotest OK 2.01s
63/121 DPDK:fast-tests / lpm6_autotest OK 7.61s
64/121 DPDK:fast-tests / malloc_autotest OK 0.40s
65/121 DPDK:fast-tests / mbuf_autotest OK 0.19s
66/121 DPDK:fast-tests / mcslock_autotest OK 0.53s
67/121 DPDK:fast-tests / member_autotest OK 1.84s
68/121 DPDK:fast-tests / memcpy_autotest OK 2.17s
69/121 DPDK:fast-tests / memory_autotest OK 0.14s
70/121 DPDK:fast-tests / mempool_autotest OK 0.49s
71/121 DPDK:fast-tests / memzone_autotest OK 0.15s
72/121 DPDK:fast-tests / meter_autotest OK 0.17s
73/121 DPDK:fast-tests / metrics_autotest OK 0.17s
74/121 DPDK:fast-tests / multiprocess_autotest OK 0.25s
75/121 DPDK:fast-tests / net_ether_autotest OK 0.45s
76/121 DPDK:fast-tests / net_ipv6_autotest OK 0.17s
77/121 DPDK:fast-tests / pcapng_autotest OK 8.22s
78/121 DPDK:fast-tests / pdcp_autotest SKIP 0.16s exit status 77
79/121 DPDK:fast-tests / pdump_autotest OK 0.35s
80/121 DPDK:fast-tests / per_lcore_autotest OK 0.29s
81/121 DPDK:fast-tests / pflock_autotest OK 0.43s
82/121 DPDK:fast-tests / pie_autotest OK 0.29s
83/121 DPDK:fast-tests / ring_pmd_autotest OK 0.24s
84/121 DPDK:fast-tests / power_autotest OK 0.35s
85/121 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.15s exit status 77
86/121 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.20s exit status 77
87/121 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.16s exit status 77
88/121 DPDK:fast-tests / prefetch_autotest OK 0.20s
89/121 DPDK:fast-tests / ptr_compress_autotest OK 0.19s
90/121 DPDK:fast-tests / rawdev_autotest OK 0.19s
91/121 DPDK:fast-tests / rcu_qsbr_autotest OK 0.29s
92/121 DPDK:fast-tests / reorder_autotest OK 0.61s
93/121 DPDK:fast-tests / rib_autotest OK 9.23s
94/121 DPDK:fast-tests / rib6_autotest OK 10.07s
95/121 DPDK:fast-tests / ring_autotest OK 0.20s
96/121 DPDK:fast-tests / rwlock_test1_autotest OK 0.29s
97/121 DPDK:fast-tests / rwlock_rda_autotest OK 5.27s
98/121 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.27s
99/121 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.26s
100/121 DPDK:fast-tests / sched_autotest OK 0.30s
101/121 DPDK:fast-tests / security_autotest OK 0.16s
102/121 DPDK:fast-tests / seqlock_autotest SKIP 0.53s exit status 77
103/121 DPDK:fast-tests / service_autotest OK 0.40s
104/121 DPDK:fast-tests / soring_autotest OK 0.31s
105/121 DPDK:fast-tests / spinlock_autotest OK 0.18s
106/121 DPDK:fast-tests / stack_autotest OK 0.19s
107/121 DPDK:fast-tests / stack_lf_autotest OK 0.60s
108/121 DPDK:fast-tests / string_autotest OK 0.46s
109/121 DPDK:fast-tests / table_autotest OK 8.04s
110/121 DPDK:fast-tests / tailq_autotest OK 0.18s
111/121 DPDK:fast-tests / telemetry_data_autotest OK 0.27s
112/121 DPDK:fast-tests / telemetry_json_autotest OK 0.31s
113/121 DPDK:fast-tests / thash_autotest OK 1.04s
114/121 DPDK:fast-tests / threads_autotest OK 1.48s
115/121 DPDK:fast-tests / ticketlock_autotest OK 0.70s
116/121 DPDK:fast-tests / timer_autotest OK 2.60s
117/121 DPDK:fast-tests / trace_autotest OK 0.23s
118/121 DPDK:fast-tests / trace_autotest_with_traces OK 0.49s
119/121 DPDK:fast-tests / vdev_autotest OK 0.48s
120/121 DPDK:fast-tests / version_autotest OK 0.22s
121/121 DPDK:fast-tests / telemetry_all OK 1.34s
Ok: 111
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: 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
Red Hat Enterprise Linux 9.5
Kernel: 5.15
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-2)
CentOS Stream 9
Kernel: 5.15
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-7)
Fedora Linux 40
Kernel: 5.15
Compiler: gcc gcc (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3)
Red Hat Enterprise Linux 8.10
Kernel: 5.15
Compiler: gcc gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-22)
Fedora Linux 41
Kernel: 5.15
Compiler: clang gcc (GCC) 14.3.1 20250523 (Red Hat 14.3.1-1)
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
Ubuntu 22.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.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/33565/
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-07-02 18:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250702095144.3087250-6-g.singh@nxp.com>
2025-07-02 9:35 ` |SUCCESS| pw154953-154957 [PATCH v8 5/5] net/dpaa2: enable software taildrop for ordered queues qemudev
2025-07-02 9:39 ` qemudev
2025-07-02 9:51 ` |SUCCESS| pw154957 " checkpatch
2025-07-02 11:03 ` 0-day Robot
2025-07-02 16:46 ` |SUCCESS| pw154953-154957 [PATCH] [v8,5/5] net/dpaa2: enable softwar dpdklab
2025-07-02 16:48 ` |PENDING| " dpdklab
2025-07-02 16:55 ` |SUCCESS| " dpdklab
2025-07-02 17:06 ` |PENDING| " dpdklab
2025-07-02 17:09 ` dpdklab
2025-07-02 17:16 ` dpdklab
2025-07-02 17:25 ` |SUCCESS| " dpdklab
2025-07-02 17:37 ` dpdklab
2025-07-02 18:05 ` dpdklab
2025-07-02 18:40 ` dpdklab
2025-07-02 18:40 ` dpdklab
2025-07-02 18:55 ` dpdklab [this message]
2025-07-02 19:00 ` |FAILURE| " dpdklab
2025-07-02 20:57 ` |PENDING| " dpdklab
2025-07-02 21:07 ` |SUCCESS| " dpdklab
2025-07-02 21:09 ` dpdklab
2025-07-02 21:09 ` dpdklab
2025-07-02 21:10 ` dpdklab
2025-07-02 21:10 ` dpdklab
2025-07-02 21:11 ` dpdklab
2025-07-02 21:19 ` |WARNING| " dpdklab
2025-07-02 21:41 ` 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=686580a8.170a0220.11eb9a.0e4fSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=g.singh@nxp.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).