From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Stephen Hemminger <stephen@networkplumber.org>,
Gregory Etelson <getelson@nvidia.com>
Subject: |FAILURE| pw158180-158181 [PATCH] [2/2] net/mlx5: support PF represe
Date: Tue, 28 Oct 2025 07:52:43 -0700 (PDT) [thread overview]
Message-ID: <6900d8bb.050a0220.3056d4.30a5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251028095831.53669-2-getelson@nvidia.com>
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/158181
_Testing issues_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Tuesday, October 28 2025 09:58:30
DPDK git baseline: Repo:dpdk-next-net
Branch: master
CommitID:11a6a4b1f19140ac3a57ace844be3cba00c39eaa
158180-158181 --> testing issues
Upstream job id: Generic-Unit-Test-DPDK#386090
Test environment and result as below:
+-------------------------------+----------------+
| Environment | dpdk_unit_test |
+===============================+================+
| CentOS Stream 10 | PEND |
+-------------------------------+----------------+
| Debian GNU/Linux 12 | FAIL |
+-------------------------------+----------------+
| CentOS Stream 9 | PEND |
+-------------------------------+----------------+
| Fedora Linux 40 | PEND |
+-------------------------------+----------------+
| Fedora Linux 42 | PEND |
+-------------------------------+----------------+
| Fedora Linux 41 | PEND |
+-------------------------------+----------------+
| Red Hat Enterprise Linux 9.5 | PEND |
+-------------------------------+----------------+
| Red Hat Enterprise Linux 8.10 | PEND |
+-------------------------------+----------------+
| Ubuntu 20.04 | PEND |
+-------------------------------+----------------+
| Ubuntu 22.04 | PEND |
+-------------------------------+----------------+
| Ubuntu 24.04 | PEND |
+-------------------------------+----------------+
==== Unit test summary for Debian GNU/Linux 12 (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 6.66s
2/120 DPDK:fast-tests / alarm_autotest OK 1.46s
3/120 DPDK:fast-tests / argparse_autotest OK 0.36s
4/120 DPDK:fast-tests / atomic_autotest OK 0.74s
5/120 DPDK:fast-tests / bitcount_autotest OK 0.17s
6/120 DPDK:fast-tests / bitmap_autotest OK 0.29s
7/120 DPDK:fast-tests / bitops_autotest OK 1.84s
8/120 DPDK:fast-tests / bitratestats_autotest OK 0.34s
9/120 DPDK:fast-tests / bitset_autotest OK 3.67s
10/120 DPDK:fast-tests / bpf_autotest OK 0.31s
11/120 DPDK:fast-tests / bpf_convert_autotest OK 0.31s
12/120 DPDK:fast-tests / byteorder_autotest OK 0.17s
13/120 DPDK:fast-tests / cfgfile_autotest OK 0.36s
14/120 DPDK:fast-tests / cksum_autotest OK 0.27s
15/120 DPDK:fast-tests / cmdline_autotest OK 0.48s
16/120 DPDK:fast-tests / common_autotest OK 1.07s
17/120 DPDK:fast-tests / compressdev_autotest SKIP 0.32s exit status 77
18/120 DPDK:fast-tests / cpuflags_autotest OK 0.38s
19/120 DPDK:fast-tests / crc_autotest OK 0.46s
20/120 DPDK:fast-tests / user_delay_us OK 0.32s
21/120 DPDK:fast-tests / debug_autotest OK 2.12s
22/120 DPDK:fast-tests / devargs_autotest FAIL 35.62s killed by signal 11 SIGSEGV
>>> DPDK_TEST=devargs_autotest MALLOC_PERTURB_=62 /root/workspace/Generic-Unit-Test-DPDK/dpdk/build/app/dpdk-test --no-huge -m 2048
23/120 DPDK:fast-tests / dispatcher_autotest SKIP 0.21s exit status 77
24/120 DPDK:fast-tests / distributor_autotest OK 2.35s
25/120 DPDK:fast-tests / eal_flags_c_opt_autotest OK 2.24s
26/120 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.61s
27/120 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.75s
28/120 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.54s
29/120 DPDK:fast-tests / eal_flags_no_huge_autotest OK 1.03s
30/120 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.87s
31/120 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.80s
32/120 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.71s
33/120 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.57s
34/120 DPDK:fast-tests / eal_flags_mem_autotest OK 1.58s
35/120 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 6.68s
36/120 DPDK:fast-tests / eal_flags_misc_autotest OK 4.37s
37/120 DPDK:fast-tests / eal_fs_autotest OK 0.30s
38/120 DPDK:fast-tests / errno_autotest OK 0.45s
39/120 DPDK:fast-tests / ethdev_link_status OK 0.23s
40/120 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.14s
41/120 DPDK:fast-tests / event_ring_autotest OK 0.54s
42/120 DPDK:fast-tests / eventdev_common_autotest OK 0.43s
43/120 DPDK:fast-tests / eventdev_selftest_sw OK 0.84s
44/120 DPDK:fast-tests / fbarray_autotest OK 0.45s
45/120 DPDK:fast-tests / fib_autotest OK 2.21s
46/120 DPDK:fast-tests / fib6_autotest OK 2.78s
47/120 DPDK:fast-tests / func_reentrancy_autotest OK 1.09s
48/120 DPDK:fast-tests / graph_autotest OK 0.56s
49/120 DPDK:fast-tests / node_list_dump OK 0.32s
50/120 DPDK:fast-tests / graph_feature_arc_autotest OK 0.18s
51/120 DPDK:fast-tests / hash_autotest OK 0.55s
52/120 DPDK:fast-tests / hash_readwrite_func_autotest SKIP 0.30s exit status 77
53/120 DPDK:fast-tests / interrupt_autotest OK 2.15s
54/120 DPDK:fast-tests / ipfrag_autotest OK 0.23s
55/120 DPDK:fast-tests / ipsec_autotest SKIP 0.43s exit status 77
56/120 DPDK:fast-tests / kvargs_autotest OK 0.47s
57/120 DPDK:fast-tests / latencystats_autotest OK 0.34s
58/120 DPDK:fast-tests / lcore_var_autotest OK 0.63s
59/120 DPDK:fast-tests / lcores_autotest OK 1.62s
60/120 DPDK:fast-tests / logs_autotest OK 0.22s
61/120 DPDK:fast-tests / lpm_autotest OK 4.04s
62/120 DPDK:fast-tests / lpm6_autotest OK 10.09s
63/120 DPDK:fast-tests / malloc_autotest OK 0.98s
64/120 DPDK:fast-tests / mbuf_autotest OK 0.37s
65/120 DPDK:fast-tests / mcslock_autotest OK 1.18s
66/120 DPDK:fast-tests / member_autotest OK 2.22s
67/120 DPDK:fast-tests / memcpy_autotest OK 4.87s
68/120 DPDK:fast-tests / memory_autotest OK 0.33s
69/120 DPDK:fast-tests / mempool_autotest OK 0.61s
70/120 DPDK:fast-tests / memzone_autotest OK 0.24s
71/120 DPDK:fast-tests / meter_autotest OK 0.53s
72/120 DPDK:fast-tests / metrics_autotest OK 0.36s
73/120 DPDK:fast-tests / multiprocess_autotest OK 0.53s
74/120 DPDK:fast-tests / net_ether_autotest OK 1.06s
75/120 DPDK:fast-tests / net_ipv6_autotest OK 0.28s
76/120 DPDK:fast-tests / pcapng_autotest OK 10.60s
77/120 DPDK:fast-tests / pdcp_autotest SKIP 0.30s exit status 77
78/120 DPDK:fast-tests / pdump_autotest OK 0.85s
79/120 DPDK:fast-tests / per_lcore_autotest OK 0.37s
80/120 DPDK:fast-tests / pflock_autotest OK 0.47s
81/120 DPDK:fast-tests / pie_autotest OK 0.31s
82/120 DPDK:fast-tests / ring_pmd_autotest OK 0.30s
83/120 DPDK:fast-tests / power_autotest OK 0.23s
84/120 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.29s exit status 77
85/120 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.18s exit status 77
86/120 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.25s exit status 77
87/120 DPDK:fast-tests / prefetch_autotest OK 0.32s
88/120 DPDK:fast-tests / ptr_compress_autotest OK 0.29s
89/120 DPDK:fast-tests / rawdev_autotest OK 0.34s
90/120 DPDK:fast-tests / rcu_qsbr_autotest OK 0.48s
91/120 DPDK:fast-tests / reorder_autotest OK 0.75s
92/120 DPDK:fast-tests / rib_autotest OK 11.97s
93/120 DPDK:fast-tests / rib6_autotest OK 10.89s
94/120 DPDK:fast-tests / ring_autotest OK 0.37s
95/120 DPDK:fast-tests / rwlock_test1_autotest OK 0.56s
96/120 DPDK:fast-tests / rwlock_rda_autotest OK 5.30s
97/120 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.29s
98/120 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.22s
99/120 DPDK:fast-tests / sched_autotest OK 0.29s
100/120 DPDK:fast-tests / security_autotest OK 0.22s
101/120 DPDK:fast-tests / seqlock_autotest SKIP 0.28s exit status 77
102/120 DPDK:fast-tests / service_autotest OK 0.34s
103/120 DPDK:fast-tests / soring_autotest OK 0.66s
104/120 DPDK:fast-tests / spinlock_autotest OK 0.27s
105/120 DPDK:fast-tests / stack_autotest OK 0.28s
106/120 DPDK:fast-tests / stack_lf_autotest OK 0.57s
107/120 DPDK:fast-tests / string_autotest OK 0.23s
108/120 DPDK:fast-tests / table_autotest OK 16.44s
109/120 DPDK:fast-tests / tailq_autotest OK 0.26s
110/120 DPDK:fast-tests / telemetry_data_autotest OK 0.44s
111/120 DPDK:fast-tests / telemetry_json_autotest OK 0.32s
112/120 DPDK:fast-tests / thash_autotest OK 0.29s
113/120 DPDK:fast-tests / threads_autotest OK 0.89s
114/120 DPDK:fast-tests / ticketlock_autotest OK 0.31s
115/120 DPDK:fast-tests / timer_autotest OK 3.00s
116/120 DPDK:fast-tests / trace_autotest OK 0.32s
117/120 DPDK:fast-tests / trace_autotest_with_traces OK 0.29s
118/120 DPDK:fast-tests / vdev_autotest OK 0.20s
119/120 DPDK:fast-tests / version_autotest OK 0.30s
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 devargs_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
CentOS Stream 9
Kernel: 5.15
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-11)
Fedora Linux 40
Kernel: 5.15
Compiler: gcc gcc (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3)
Fedora Linux 42
Kernel: 5.15
Compiler: gcc gcc (GCC) 15.2.1 20250808 (Red Hat 15.2.1-1)
Fedora Linux 41
Kernel: 5.15
Compiler: gcc gcc (GCC) 14.3.1 20250523 (Red Hat 14.3.1-1)
Red Hat Enterprise Linux 9.5
Kernel: 5.15
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-2)
Red Hat Enterprise Linux 8.10
Kernel: 5.15
Compiler: gcc gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-22)
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/34399/
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-10-28 14:52 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251028095831.53669-2-getelson@nvidia.com>
2025-10-28 9:34 ` |SUCCESS| pw158180-158181 [PATCH 2/2] net/mlx5: support PF representor suppresion in multi-port E-Switch qemudev
2025-10-28 9:39 ` |FAILURE| " qemudev
2025-10-28 10:00 ` |WARNING| pw158181 " checkpatch
2025-10-28 11:13 ` |SUCCESS| pw158180-158181 [PATCH] [2/2] net/mlx5: support PF represe dpdklab
2025-10-28 11:19 ` dpdklab
2025-10-28 11:20 ` |PENDING| " dpdklab
2025-10-28 11:22 ` |SUCCESS| " dpdklab
2025-10-28 11:22 ` |FAILURE| pw158181 [PATCH 2/2] net/mlx5: support PF representor suppresion in multi-port E-Switch 0-day Robot
2025-10-28 11:29 ` |SUCCESS| pw158180-158181 [PATCH] [2/2] net/mlx5: support PF represe dpdklab
2025-10-28 12:10 ` dpdklab
2025-10-28 12:32 ` dpdklab
2025-10-28 12:49 ` |PENDING| " dpdklab
2025-10-28 13:11 ` dpdklab
2025-10-28 13:16 ` |SUCCESS| " dpdklab
2025-10-28 13:16 ` dpdklab
2025-10-28 13:56 ` |WARNING| " dpdklab
2025-10-28 14:52 ` dpdklab [this message]
2025-10-28 15:53 ` dpdklab
2025-10-28 16:06 ` dpdklab
2025-10-28 16:10 ` |FAILURE| " dpdklab
2025-10-28 16:57 ` |SUCCESS| " dpdklab
2025-10-28 17:18 ` |WARNING| " dpdklab
2025-10-28 17:31 ` |FAILURE| " dpdklab
2025-10-28 17:44 ` |SUCCESS| " dpdklab
2025-10-28 18:05 ` |FAILURE| " dpdklab
2025-10-28 18:25 ` |SUCCESS| " dpdklab
2025-10-28 18:49 ` |FAILURE| " dpdklab
2025-10-28 20:58 ` dpdklab
2025-10-28 21:02 ` |WARNING| " dpdklab
2025-10-28 21:30 ` 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=6900d8bb.050a0220.3056d4.30a5SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=getelson@nvidia.com \
--cc=stephen@networkplumber.org \
--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).