From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Andre Muezerie <andremue@linux.microsoft.com>
Subject: |FAILURE| pw151296 [PATCH] mbuf: enable to be compiled with MSVC
Date: Tue, 11 Feb 2025 06:59:28 -0800 (PST) [thread overview]
Message-ID: <67ab65d0.250a0220.c22c.4412SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1739224265-4158-1-git-send-email-andremue@linux.microsoft.com>
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/151296
_Testing issues_
Submitter: Andre Muezerie <andremue@linux.microsoft.com>
Date: Monday, February 10 2025 21:51:05
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:9d29cd6dc87d6c35c52194a5f7a34f2d84140353
151296 --> testing issues
Upstream job id: Generic-Unit-Test-DPDK#314091
Test environment and result as below:
+-------------------+----------------+
| Environment | dpdk_unit_test |
+===================+================+
| CentOS Stream 9 | PASS |
+-------------------+----------------+
| CentOS Stream 10 | PASS |
+-------------------+----------------+
| Fedora 40 | PASS |
+-------------------+----------------+
| Debian 12 | FAIL |
+-------------------+----------------+
| Debian Bullseye | PEND |
+-------------------+----------------+
| Fedora 40 (Clang) | PEND |
+-------------------+----------------+
| Fedora 41 | PEND |
+-------------------+----------------+
| Fedora 41 (Clang) | PEND |
+-------------------+----------------+
| RHEL8 | PEND |
+-------------------+----------------+
| Ubuntu 24.04 | PEND |
+-------------------+----------------+
| RHEL9 | PEND |
+-------------------+----------------+
| Ubuntu 22.04 | PEND |
+-------------------+----------------+
| Ubuntu 20.04 | PEND |
+-------------------+----------------+
==== Unit test summary for Debian 12 (dpdk_unit_test): ====
ninja: Entering directory `/root/workspace/Generic-Unit-Test-DPDK/dpdk/build'
ninja: no work to do.
1/119 DPDK:fast-tests / acl_autotest OK 4.82s
2/119 DPDK:fast-tests / alarm_autotest OK 1.21s
3/119 DPDK:fast-tests / argparse_autotest OK 0.19s
4/119 DPDK:fast-tests / atomic_autotest OK 0.41s
5/119 DPDK:fast-tests / bitcount_autotest OK 0.19s
6/119 DPDK:fast-tests / bitmap_autotest OK 0.26s
7/119 DPDK:fast-tests / bitops_autotest OK 1.86s
8/119 DPDK:fast-tests / bitratestats_autotest OK 0.26s
9/119 DPDK:fast-tests / bitset_autotest OK 2.65s
10/119 DPDK:fast-tests / bpf_autotest OK 0.19s
11/119 DPDK:fast-tests / bpf_convert_autotest OK 0.19s
12/119 DPDK:fast-tests / byteorder_autotest OK 0.18s
13/119 DPDK:fast-tests / cfgfile_autotest OK 0.18s
14/119 DPDK:fast-tests / cksum_autotest OK 0.18s
15/119 DPDK:fast-tests / cmdline_autotest OK 0.20s
16/119 DPDK:fast-tests / common_autotest OK 0.80s
17/119 DPDK:fast-tests / compressdev_autotest SKIP 0.16s exit status 77
18/119 DPDK:fast-tests / cpuflags_autotest OK 0.19s
19/119 DPDK:fast-tests / crc_autotest OK 0.18s
20/119 DPDK:fast-tests / user_delay_us OK 0.18s
21/119 DPDK:fast-tests / debug_autotest OK 0.51s
22/119 DPDK:fast-tests / devargs_autotest OK 0.18s
23/119 DPDK:fast-tests / dispatcher_autotest SKIP 0.16s exit status 77
24/119 DPDK:fast-tests / distributor_autotest OK 1.03s
25/119 DPDK:fast-tests / eal_flags_c_opt_autotest OK 0.79s
26/119 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.29s
27/119 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.47s
28/119 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.20s
29/119 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.49s
30/119 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.37s
31/119 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.31s
32/119 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.56s
33/119 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.26s
34/119 DPDK:fast-tests / eal_flags_mem_autotest OK 0.73s
35/119 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 2.05s
36/119 DPDK:fast-tests / eal_flags_misc_autotest FAIL 2.23s killed by signal 11 SIGSEGV
>>> DPDK_TEST=eal_flags_misc_autotest MALLOC_PERTURB_=248 /root/workspace/Generic-Unit-Test-DPDK/dpdk/build/app/dpdk-test
37/119 DPDK:fast-tests / eal_fs_autotest OK 0.17s
38/119 DPDK:fast-tests / errno_autotest OK 0.17s
39/119 DPDK:fast-tests / ethdev_link_status OK 0.17s
40/119 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 0.45s
41/119 DPDK:fast-tests / event_ring_autotest OK 0.17s
42/119 DPDK:fast-tests / eventdev_common_autotest OK 0.17s
43/119 DPDK:fast-tests / eventdev_selftest_sw OK 0.20s
44/119 DPDK:fast-tests / fbarray_autotest OK 0.16s
45/119 DPDK:fast-tests / fib_autotest OK 0.67s
46/119 DPDK:fast-tests / fib6_autotest OK 0.55s
47/119 DPDK:fast-tests / func_reentrancy_autotest OK 0.53s
48/119 DPDK:fast-tests / graph_autotest OK 0.17s
49/119 DPDK:fast-tests / node_list_dump OK 0.17s
50/119 DPDK:fast-tests / hash_autotest OK 0.26s
51/119 DPDK:fast-tests / hash_readwrite_func_autotest SKIP 0.14s exit status 77
52/119 DPDK:fast-tests / interrupt_autotest OK 1.18s
53/119 DPDK:fast-tests / ipfrag_autotest OK 0.14s
54/119 DPDK:fast-tests / ipsec_autotest SKIP 0.17s exit status 77
55/119 DPDK:fast-tests / kvargs_autotest OK 0.17s
56/119 DPDK:fast-tests / latencystats_autotest OK 0.17s
57/119 DPDK:fast-tests / lcore_var_autotest OK 0.29s
58/119 DPDK:fast-tests / lcores_autotest OK 0.73s
59/119 DPDK:fast-tests / logs_autotest OK 0.17s
60/119 DPDK:fast-tests / lpm_autotest OK 1.45s
61/119 DPDK:fast-tests / lpm6_autotest OK 2.47s
62/119 DPDK:fast-tests / malloc_autotest OK 0.34s
63/119 DPDK:fast-tests / mbuf_autotest OK 0.17s
64/119 DPDK:fast-tests / mcslock_autotest OK 0.40s
65/119 DPDK:fast-tests / member_autotest OK 0.78s
66/119 DPDK:fast-tests / memcpy_autotest OK 1.72s
67/119 DPDK:fast-tests / memory_autotest OK 0.14s
68/119 DPDK:fast-tests / mempool_autotest OK 0.42s
69/119 DPDK:fast-tests / memzone_autotest OK 0.15s
70/119 DPDK:fast-tests / meter_autotest OK 0.17s
71/119 DPDK:fast-tests / metrics_autotest OK 0.17s
72/119 DPDK:fast-tests / multiprocess_autotest OK 0.25s
73/119 DPDK:fast-tests / net_ether_autotest OK 0.49s
74/119 DPDK:fast-tests / net_ipv6_autotest OK 0.17s
75/119 DPDK:fast-tests / pcapng_autotest OK 6.83s
76/119 DPDK:fast-tests / pdcp_autotest SKIP 0.16s exit status 77
77/119 DPDK:fast-tests / pdump_autotest OK 0.28s
78/119 DPDK:fast-tests / per_lcore_autotest OK 0.27s
79/119 DPDK:fast-tests / pflock_autotest OK 0.27s
80/119 DPDK:fast-tests / pie_autotest OK 0.17s
81/119 DPDK:fast-tests / ring_pmd_autotest OK 0.17s
82/119 DPDK:fast-tests / power_autotest OK 0.16s
83/119 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.14s exit status 77
84/119 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.17s exit status 77
85/119 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.14s exit status 77
86/119 DPDK:fast-tests / prefetch_autotest OK 0.17s
87/119 DPDK:fast-tests / ptr_compress_autotest OK 0.16s
88/119 DPDK:fast-tests / rawdev_autotest OK 0.17s
89/119 DPDK:fast-tests / rcu_qsbr_autotest OK 0.26s
90/119 DPDK:fast-tests / reorder_autotest OK 0.27s
91/119 DPDK:fast-tests / rib_autotest OK 3.56s
92/119 DPDK:fast-tests / rib6_autotest OK 3.47s
93/119 DPDK:fast-tests / ring_autotest OK 0.17s
94/119 DPDK:fast-tests / rwlock_test1_autotest OK 0.27s
95/119 DPDK:fast-tests / rwlock_rda_autotest OK 5.17s
96/119 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.31s
97/119 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.17s
98/119 DPDK:fast-tests / sched_autotest OK 0.17s
99/119 DPDK:fast-tests / security_autotest OK 0.14s
100/119 DPDK:fast-tests / seqlock_autotest SKIP 0.17s exit status 77
101/119 DPDK:fast-tests / service_autotest OK 0.27s
102/119 DPDK:fast-tests / soring_autotest OK 0.17s
103/119 DPDK:fast-tests / spinlock_autotest OK 0.18s
104/119 DPDK:fast-tests / stack_autotest OK 0.18s
105/119 DPDK:fast-tests / stack_lf_autotest OK 0.23s
106/119 DPDK:fast-tests / string_autotest OK 0.17s
107/119 DPDK:fast-tests / table_autotest OK 4.68s
108/119 DPDK:fast-tests / tailq_autotest OK 0.17s
109/119 DPDK:fast-tests / telemetry_data_autotest OK 0.17s
110/119 DPDK:fast-tests / telemetry_json_autotest OK 0.16s
111/119 DPDK:fast-tests / thash_autotest OK 0.17s
112/119 DPDK:fast-tests / threads_autotest OK 0.33s
113/119 DPDK:fast-tests / ticketlock_autotest OK 0.18s
114/119 DPDK:fast-tests / timer_autotest OK 2.48s
115/119 DPDK:fast-tests / trace_autotest OK 0.17s
116/119 DPDK:fast-tests / trace_autotest_with_traces OK 0.17s
117/119 DPDK:fast-tests / vdev_autotest OK 0.17s
118/119 DPDK:fast-tests / version_autotest OK 0.17s
119/119 DPDK:fast-tests / telemetry_all SKIP 0.01s exit status 77
Ok: 108
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 ====
CentOS Stream 9
Kernel: Depends on container host
Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)
CentOS Stream 10
Kernel: Depends on container host
Compiler: gcc 14.2.1 20241104 (Red Hat 14.2.1-6)
Fedora 40
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)
Debian 12
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
Debian Bullseye
Kernel: Depends on container host
Compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110
Fedora 40 (Clang)
Kernel: Depends on container host
Compiler: clang 18.1.8 (Fedora 18.1.8-1.fc40)
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)
RHEL8
Kernel: Depends on container host
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-22)
Ubuntu 24.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
RHEL9
Kernel: Depends on container host
Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)
Ubuntu 22.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Ubuntu 20.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32556/
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-02-11 14:59 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1739224265-4158-1-git-send-email-andremue@linux.microsoft.com>
2025-02-10 21:19 ` |SUCCESS| " qemudev
2025-02-10 21:23 ` qemudev
2025-02-10 21:51 ` checkpatch
2025-02-10 23:05 ` 0-day Robot
2025-02-11 12:15 ` |FAILURE| " dpdklab
2025-02-11 12:23 ` |SUCCESS| " dpdklab
2025-02-11 12:29 ` dpdklab
2025-02-11 12:35 ` dpdklab
2025-02-11 12:36 ` dpdklab
2025-02-11 12:41 ` dpdklab
2025-02-11 12:50 ` dpdklab
2025-02-11 13:00 ` dpdklab
2025-02-11 13:02 ` dpdklab
2025-02-11 13:04 ` dpdklab
2025-02-11 13:07 ` dpdklab
2025-02-11 13:15 ` dpdklab
2025-02-11 13:16 ` dpdklab
2025-02-11 13:25 ` |PENDING| " dpdklab
2025-02-11 13:30 ` dpdklab
2025-02-11 13:36 ` dpdklab
2025-02-11 13:37 ` |SUCCESS| " dpdklab
2025-02-11 14:07 ` |PENDING| " dpdklab
2025-02-11 14:09 ` dpdklab
2025-02-11 14:26 ` |SUCCESS| " dpdklab
2025-02-11 14:28 ` dpdklab
2025-02-11 14:28 ` dpdklab
2025-02-11 14:29 ` dpdklab
2025-02-11 14:41 ` |PENDING| " dpdklab
2025-02-11 14:51 ` dpdklab
2025-02-11 14:52 ` dpdklab
2025-02-11 14:53 ` |SUCCESS| " dpdklab
2025-02-11 14:59 ` dpdklab [this message]
2025-02-11 15:04 ` |PENDING| " dpdklab
2025-02-11 15:17 ` |SUCCESS| " dpdklab
2025-02-11 15:39 ` |FAILURE| " dpdklab
2025-02-11 15:47 ` |SUCCESS| " dpdklab
2025-02-11 16:04 ` dpdklab
2025-02-11 16:09 ` |FAILURE| " dpdklab
2025-02-11 16:17 ` |SUCCESS| " dpdklab
2025-02-11 16:36 ` dpdklab
2025-02-11 16:41 ` dpdklab
2025-02-11 17:21 ` dpdklab
2025-02-11 17:22 ` 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=67ab65d0.250a0220.c22c.4412SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=andremue@linux.microsoft.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).