From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>
Subject: |FAILURE| [GIT MASTER] db0eb7fb7bc68dd241029ae2cc46f487ef712d1a
Date: Wed, 27 Nov 2024 11:29:48 -0800 (PST) [thread overview]
Message-ID: <6747732c.810a0220.145074.62faSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing issues_
Branch: 21.11-staging
db0eb7fb7bc68dd241029ae2cc46f487ef712d1a --> testing issues
Upstream job id: Generic-Unit-Test-DPDK#295769
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Debian 12 | FAIL |
+---------------------+----------------+
| CentOS Stream 9 | FAIL |
+---------------------+----------------+
| Fedora 39 (Clang) | FAIL |
+---------------------+----------------+
| Fedora 39 | FAIL |
+---------------------+----------------+
| RHEL8 | PEND |
+---------------------+----------------+
| Fedora 40 | PEND |
+---------------------+----------------+
| RHEL9 | FAIL |
+---------------------+----------------+
| Fedora 40 (Clang) | FAIL |
+---------------------+----------------+
| Ubuntu 20.04 | PEND |
+---------------------+----------------+
| Ubuntu 24.04 | PEND |
+---------------------+----------------+
| Ubuntu 22.04 | PEND |
+---------------------+----------------+
| Windows Server 2022 | PASS |
+---------------------+----------------+
==== Unit test summary for Fedora 40 (Clang) (dpdk_unit_test): ====
ninja: Entering directory `/home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/build'
ninja: no work to do.
1/101 DPDK:fast-tests / acl_autotest OK 2.79 s
2/101 DPDK:fast-tests / atomic_autotest OK 0.40 s
3/101 DPDK:fast-tests / bitmap_autotest OK 0.19 s
4/101 DPDK:fast-tests / bpf_autotest OK 0.19 s
5/101 DPDK:fast-tests / bpf_convert_autotest OK 0.17 s
6/101 DPDK:fast-tests / bitops_autotest OK 0.17 s
7/101 DPDK:fast-tests / byteorder_autotest OK 0.18 s
8/101 DPDK:fast-tests / cksum_autotest OK 0.22 s
9/101 DPDK:fast-tests / cmdline_autotest OK 0.17 s
10/101 DPDK:fast-tests / common_autotest OK 0.42 s
11/101 DPDK:fast-tests / cpuflags_autotest OK 0.17 s
12/101 DPDK:fast-tests / debug_autotest OK 0.32 s
13/101 DPDK:fast-tests / devargs_autotest OK 0.17 s
14/101 DPDK:fast-tests / eal_flags_c_opt_autotest OK 0.67 s
15/101 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.30 s
16/101 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.48 s
17/101 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.22 s
18/101 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.53 s
19/101 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.32 s
20/101 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.32 s
21/101 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.57 s
22/101 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.27 s
23/101 DPDK:fast-tests / eal_flags_mem_autotest OK 0.75 s
24/101 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 2.02 s
25/101 DPDK:fast-tests / eal_flags_misc_autotest OK 1.68 s
26/101 DPDK:fast-tests / eal_fs_autotest OK 0.17 s
27/101 DPDK:fast-tests / errno_autotest OK 0.17 s
28/101 DPDK:fast-tests / ethdev_link_status OK 0.16 s
29/101 DPDK:fast-tests / event_ring_autotest OK 0.17 s
30/101 DPDK:fast-tests / fib_autotest OK 0.83 s
31/101 DPDK:fast-tests / fib6_autotest OK 0.80 s
32/101 DPDK:fast-tests / func_reentrancy_autotest OK 0.77 s
33/101 DPDK:fast-tests / flow_classify_autotest OK 0.25 s
34/101 DPDK:fast-tests / graph_autotest OK 0.17 s
35/101 DPDK:fast-tests / hash_autotest OK 0.28 s
36/101 DPDK:fast-tests / interrupt_autotest OK 1.19 s
37/101 DPDK:fast-tests / ipfrag_autotest OK 0.17 s
38/101 DPDK:fast-tests / lcores_autotest OK 2.03 s
39/101 DPDK:fast-tests / logs_autotest OK 0.24 s
40/101 DPDK:fast-tests / lpm_autotest OK 5.15 s
41/101 DPDK:fast-tests / lpm6_autotest OK 6.05 s
42/101 DPDK:fast-tests / malloc_autotest OK 0.48 s
43/101 DPDK:fast-tests / mbuf_autotest OK 0.22 s
44/101 DPDK:fast-tests / mcslock_autotest OK 0.47 s
45/101 DPDK:fast-tests / memcpy_autotest OK 1.54 s
46/101 DPDK:fast-tests / memory_autotest OK 0.21 s
47/101 DPDK:fast-tests / mempool_autotest OK 0.47 s
48/101 DPDK:fast-tests / memzone_autotest OK 0.25 s
49/101 DPDK:fast-tests / meter_autotest OK 0.24 s
50/101 DPDK:fast-tests / multiprocess_autotest OK 0.27 s
51/101 DPDK:fast-tests / node_list_dump OK 0.21 s
52/101 DPDK:fast-tests / per_lcore_autotest OK 0.26 s
53/101 DPDK:fast-tests / pflock_autotest OK 0.27 s
54/101 DPDK:fast-tests / prefetch_autotest OK 0.15 s
55/101 DPDK:fast-tests / rcu_qsbr_autotest OK 0.27 s
56/101 DPDK:fast-tests / pie_autotest OK 0.17 s
57/101 DPDK:fast-tests / rib_autotest OK 5.89 s
58/101 DPDK:fast-tests / rib6_autotest OK 5.93 s
59/101 DPDK:fast-tests / ring_autotest OK 0.17 s
60/101 DPDK:fast-tests / rwlock_test1_autotest OK 0.27 s
61/101 DPDK:fast-tests / rwlock_rda_autotest OK 5.29 s
62/101 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.26 s
63/101 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.26 s
64/101 DPDK:fast-tests / sched_autotest OK 0.17 s
65/101 DPDK:fast-tests / security_autotest OK 0.21 s
66/101 DPDK:fast-tests / spinlock_autotest OK 0.17 s
67/101 DPDK:fast-tests / stack_autotest OK 0.26 s
68/101 DPDK:fast-tests / stack_lf_autotest OK 0.31 s
69/101 DPDK:fast-tests / string_autotest OK 0.17 s
70/101 DPDK:fast-tests / table_autotest FAIL 0.94 s (exit status 255 or signal 127 SIGinvalid)
71/101 DPDK:fast-tests / tailq_autotest OK 0.17 s
72/101 DPDK:fast-tests / ticketlock_autotest OK 0.18 s
73/101 DPDK:fast-tests / timer_autotest OK 2.65 s
74/101 DPDK:fast-tests / user_delay_us OK 0.16 s
75/101 DPDK:fast-tests / version_autotest OK 0.17 s
76/101 DPDK:fast-tests / crc_autotest OK 0.16 s
77/101 DPDK:fast-tests / distributor_autotest OK 1.22 s
78/101 DPDK:fast-tests / eventdev_common_autotest OK 0.22 s
79/101 DPDK:fast-tests / fbarray_autotest OK 0.25 s
80/101 DPDK:fast-tests / hash_readwrite_func_autotest SKIP 0.17 s
81/101 DPDK:fast-tests / ipsec_autotest SKIP 0.16 s
82/101 DPDK:fast-tests / kni_autotest SKIP 0.17 s
83/101 DPDK:fast-tests / kvargs_autotest OK 0.17 s
84/101 DPDK:fast-tests / member_autotest OK 0.17 s
85/101 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.22 s
86/101 DPDK:fast-tests / power_autotest OK 0.18 s
87/101 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.17 s
88/101 DPDK:fast-tests / reorder_autotest OK 0.33 s
89/101 DPDK:fast-tests / service_autotest OK 1.35 s
90/101 DPDK:fast-tests / thash_autotest OK 0.16 s
91/101 DPDK:fast-tests / trace_autotest OK 0.19 s
92/101 DPDK:fast-tests / metrics_autotest OK 0.17 s
93/101 DPDK:fast-tests / telemetry_json_autotest OK 0.17 s
94/101 DPDK:fast-tests / telemetry_data_autotest OK 0.17 s
95/101 DPDK:fast-tests / ring_pmd_autotest OK 0.17 s
96/101 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 0.65 s
97/101 DPDK:fast-tests / bitratestats_autotest OK 0.17 s
98/101 DPDK:fast-tests / latencystats_autotest OK 0.17 s
99/101 DPDK:fast-tests / pdump_autotest OK 5.25 s
100/101 DPDK:fast-tests / vdev_autotest OK 0.19 s
101/101 DPDK:fast-tests / compressdev_autotest SKIP 0.17 s
Ok: 94
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 6
Timeout: 0
Full log written to /home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/build/meson-logs/testlog.txt
Test log output from the failed test table_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 ====
Debian 12
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
CentOS Stream 9
Kernel: Depends on container host
Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)
Fedora 39 (Clang)
Kernel: Depends on container host
Compiler: clang 17.0.6 (Fedora 17.0.6-2.fc39)
Fedora 39
Kernel: Depends on container host
Compiler: gcc 13.3.1 20240522 (Red Hat 13.3.1-1)
RHEL8
Kernel: Depends on container host
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-22)
Fedora 40
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240801 (Red Hat 14.2.1-1)
RHEL9
Kernel: Depends on container host
Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)
Fedora 40 (Clang)
Kernel: Depends on container host
Compiler: clang 18.1.6 (Fedora 18.1.6-3.fc40)
Ubuntu 20.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Ubuntu 24.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0
Ubuntu 22.04
Kernel: Depends on container host
Compiler: 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/tarballs/31759/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-11-27 19:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 19:29 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-27 22:30 dpdklab
2024-11-27 19:45 dpdklab
2024-11-27 19:37 dpdklab
2024-11-27 19:36 dpdklab
2024-11-27 19:34 dpdklab
2024-11-27 19:33 dpdklab
2024-11-27 19:18 dpdklab
2024-11-27 19:18 dpdklab
2024-11-27 19:05 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=6747732c.810a0220.145074.62faSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ktraynor@redhat.com \
--cc=test-report@dpdk.org \
--cc=xuemingl@nvidia.com \
/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).