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] 7ce7d3341d7e21c2a81f2fea8e451681d7306d77
Date: Wed, 18 Dec 2024 22:05:38 -0800 (PST) [thread overview]
Message-ID: <6763b7b2.050a0220.60999.336eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing issues_
Branch: tags/v22.11
7ce7d3341d7e21c2a81f2fea8e451681d7306d77 --> testing issues
Upstream job id: Generic-Unit-Test-DPDK#300430
Test environment and result as below:
+-------------------+----------------+
| Environment | dpdk_unit_test |
+===================+================+
| Debian 12 | FAIL |
+-------------------+----------------+
| Fedora 39 | PEND |
+-------------------+----------------+
| Fedora 40 | PEND |
+-------------------+----------------+
| CentOS Stream 9 | PEND |
+-------------------+----------------+
| Fedora 39 (Clang) | PEND |
+-------------------+----------------+
| RHEL8 | PEND |
+-------------------+----------------+
| Fedora 40 (Clang) | PEND |
+-------------------+----------------+
| Ubuntu 22.04 | PEND |
+-------------------+----------------+
| RHEL9 | PEND |
+-------------------+----------------+
| Ubuntu 24.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/105 DPDK:fast-tests / acl_autotest OK 2.78 s
2/105 DPDK:fast-tests / atomic_autotest OK 0.37 s
3/105 DPDK:fast-tests / bitmap_autotest OK 0.17 s
4/105 DPDK:fast-tests / bitops_autotest OK 0.17 s
5/105 DPDK:fast-tests / byteorder_autotest OK 0.17 s
6/105 DPDK:fast-tests / cksum_autotest OK 0.17 s
7/105 DPDK:fast-tests / cmdline_autotest OK 0.17 s
8/105 DPDK:fast-tests / common_autotest OK 0.47 s
9/105 DPDK:fast-tests / cpuflags_autotest OK 0.17 s
10/105 DPDK:fast-tests / debug_autotest OK 0.37 s
11/105 DPDK:fast-tests / devargs_autotest OK 0.17 s
12/105 DPDK:fast-tests / eal_flags_c_opt_autotest OK 0.52 s
13/105 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.27 s
14/105 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.42 s
15/105 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.22 s
16/105 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.47 s
17/105 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.32 s
18/105 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.27 s
19/105 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.52 s
20/105 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.22 s
21/105 DPDK:fast-tests / eal_flags_mem_autotest OK 0.62 s
22/105 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 3.83 s
23/105 DPDK:fast-tests / eal_flags_misc_autotest OK 1.63 s
24/105 DPDK:fast-tests / eal_fs_autotest OK 0.17 s
25/105 DPDK:fast-tests / errno_autotest OK 0.17 s
26/105 DPDK:fast-tests / ethdev_link_status OK 0.17 s
27/105 DPDK:fast-tests / event_ring_autotest OK 0.17 s
28/105 DPDK:fast-tests / fib_autotest OK 0.67 s
29/105 DPDK:fast-tests / fib6_autotest OK 0.67 s
30/105 DPDK:fast-tests / func_reentrancy_autotest OK 0.52 s
31/105 DPDK:fast-tests / hash_autotest OK 0.27 s
32/105 DPDK:fast-tests / interrupt_autotest OK 1.17 s
33/105 DPDK:fast-tests / ipfrag_autotest OK 0.17 s
34/105 DPDK:fast-tests / lcores_autotest OK 1.76 s
35/105 DPDK:fast-tests / logs_autotest OK 0.17 s
36/105 DPDK:fast-tests / lpm_autotest OK 3.33 s
37/105 DPDK:fast-tests / lpm6_autotest OK 4.63 s
38/105 DPDK:fast-tests / malloc_autotest OK 0.52 s
39/105 DPDK:fast-tests / mbuf_autotest OK 0.17 s
40/105 DPDK:fast-tests / mcslock_autotest OK 0.42 s
41/105 DPDK:fast-tests / memcpy_autotest OK 1.74 s
42/105 DPDK:fast-tests / memory_autotest OK 0.17 s
43/105 DPDK:fast-tests / mempool_autotest OK 0.42 s
44/105 DPDK:fast-tests / memzone_autotest OK 0.17 s
45/105 DPDK:fast-tests / meter_autotest OK 0.17 s
46/105 DPDK:fast-tests / multiprocess_autotest OK 0.23 s
47/105 DPDK:fast-tests / node_list_dump OK 0.17 s
48/105 DPDK:fast-tests / per_lcore_autotest OK 0.27 s
49/105 DPDK:fast-tests / pflock_autotest OK 0.27 s
50/105 DPDK:fast-tests / prefetch_autotest OK 0.17 s
51/105 DPDK:fast-tests / rcu_qsbr_autotest OK 0.27 s
52/105 DPDK:fast-tests / pie_autotest OK 0.17 s
53/105 DPDK:fast-tests / rib_autotest OK 4.08 s
54/105 DPDK:fast-tests / rib6_autotest OK 4.03 s
55/105 DPDK:fast-tests / ring_autotest OK 0.17 s
56/105 DPDK:fast-tests / rwlock_test1_autotest OK 0.27 s
57/105 DPDK:fast-tests / rwlock_rda_autotest OK 5.13 s
58/105 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.13 s
59/105 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.13 s
60/105 DPDK:fast-tests / sched_autotest OK 0.17 s
61/105 DPDK:fast-tests / security_autotest OK 0.17 s
62/105 DPDK:fast-tests / seqlock_autotest SKIP 0.17 s
63/105 DPDK:fast-tests / spinlock_autotest OK 0.17 s
64/105 DPDK:fast-tests / stack_autotest OK 0.17 s
65/105 DPDK:fast-tests / stack_lf_autotest OK 0.22 s
66/105 DPDK:fast-tests / string_autotest OK 0.17 s
67/105 DPDK:fast-tests / tailq_autotest OK 0.17 s
68/105 DPDK:fast-tests / ticketlock_autotest OK 0.17 s
69/105 DPDK:fast-tests / timer_autotest OK 2.52 s
70/105 DPDK:fast-tests / user_delay_us OK 0.17 s
71/105 DPDK:fast-tests / version_autotest OK 0.17 s
72/105 DPDK:fast-tests / crc_autotest OK 0.17 s
73/105 DPDK:fast-tests / distributor_autotest OK 0.87 s
74/105 DPDK:fast-tests / eventdev_common_autotest OK 0.17 s
75/105 DPDK:fast-tests / fbarray_autotest OK 0.17 s
76/105 DPDK:fast-tests / hash_readwrite_func_autotest SKIP 0.17 s
77/105 DPDK:fast-tests / ipsec_autotest SKIP 0.17 s
78/105 DPDK:fast-tests / kni_autotest SKIP 0.17 s
79/105 DPDK:fast-tests / kvargs_autotest OK 0.17 s
80/105 DPDK:fast-tests / member_autotest OK 0.72 s
81/105 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.17 s
82/105 DPDK:fast-tests / power_autotest OK 0.17 s
83/105 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.17 s
84/105 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.17 s
85/105 DPDK:fast-tests / reorder_autotest OK 0.22 s
86/105 DPDK:fast-tests / service_autotest OK 1.07 s
87/105 DPDK:fast-tests / thash_autotest OK 0.17 s
88/105 DPDK:fast-tests / threads_autotest OK 0.27 s
89/105 DPDK:fast-tests / trace_autotest OK 0.17 s
90/105 DPDK:fast-tests / trace_autotest_with_traces OK 0.17 s
91/105 DPDK:fast-tests / graph_autotest OK 0.17 s
92/105 DPDK:fast-tests / metrics_autotest OK 0.17 s
93/105 DPDK:fast-tests / telemetry_json_autotest OK 0.17 s
94/105 DPDK:fast-tests / telemetry_data_autotest OK 0.17 s
95/105 DPDK:fast-tests / table_autotest FAIL 0.77 s (exit status 255 or signal 127 SIGinvalid)
96/105 DPDK:fast-tests / ring_pmd_autotest OK 0.17 s
97/105 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 0.42 s
98/105 DPDK:fast-tests / bitratestats_autotest OK 0.17 s
99/105 DPDK:fast-tests / latencystats_autotest OK 0.17 s
100/105 DPDK:fast-tests / pdump_autotest OK 5.24 s
101/105 DPDK:fast-tests / vdev_autotest OK 0.17 s
102/105 DPDK:fast-tests / bpf_autotest OK 0.17 s
103/105 DPDK:fast-tests / bpf_convert_autotest OK 0.17 s
104/105 DPDK:fast-tests / compressdev_autotest SKIP 0.17 s
105/105 DPDK:fast-tests / telemetry_all SKIP 0.01 s
Ok: 95
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 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
Fedora 39
Kernel: Depends on container host
Compiler: gcc 13.3.1 20240522 (Red Hat 13.3.1-1)
Fedora 40
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240801 (Red Hat 14.2.1-1)
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)
RHEL8
Kernel: Depends on container host
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-22)
Fedora 40 (Clang)
Kernel: Depends on container host
Compiler: clang 18.1.6 (Fedora 18.1.6-3.fc40)
Ubuntu 22.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
RHEL9
Kernel: Depends on container host
Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)
Ubuntu 24.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.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/tarballs/31982/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-12-19 6:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 6:05 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-21 8:26 dpdklab
2024-12-21 7:58 dpdklab
2024-12-21 7:57 dpdklab
2024-12-21 7:09 dpdklab
2024-12-20 8:54 dpdklab
2024-12-20 8:49 dpdklab
2024-12-20 7:53 dpdklab
2024-12-19 6:54 dpdklab
2024-12-19 6:46 dpdklab
2024-12-18 10:52 dpdklab
2024-12-18 1: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=6763b7b2.050a0220.60999.336eSMTPIN_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).