From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Morten Brorup <mb@smartsharesystems.com>
Subject: |FAILURE| pw148030 [PATCH] [TEST,v11] ethdev: test single queue per
Date: Thu, 07 Nov 2024 03:19:04 -0800 (PST) [thread overview]
Message-ID: <672ca228.050a0220.2323a7.30d7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241107092649.1507375-1-mb@smartsharesystems.com>
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/148030
_Testing issues_
Submitter: Morten Brorup <mb@smartsharesystems.com>
Date: Thursday, November 07 2024 09:26:49
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:9bbd44d63846cf0771ec0f1c7e1b5a63ec5e9603
148030 --> testing issues
Upstream job id: Generic-Unit-Test-DPDK#289062
Test environment and result as below:
+-------------------+----------------+
| Environment | dpdk_unit_test |
+===================+================+
| Debian 12 | FAIL |
+-------------------+----------------+
| CentOS Stream 9 | PEND |
+-------------------+----------------+
| Fedora 39 (Clang) | PEND |
+-------------------+----------------+
| Fedora 39 | PEND |
+-------------------+----------------+
| Fedora 40 | PEND |
+-------------------+----------------+
| RHEL8 | PEND |
+-------------------+----------------+
| RHEL9 | PEND |
+-------------------+----------------+
| Fedora 40 (Clang) | PEND |
+-------------------+----------------+
| Ubuntu 20.04 | PEND |
+-------------------+----------------+
| Ubuntu 22.04 | PEND |
+-------------------+----------------+
| Ubuntu 24.04 | PEND |
+-------------------+----------------+
==== Unit test summary for Debian 12 (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/116 DPDK:fast-tests / acl_autotest OK 2.61s
2/116 DPDK:fast-tests / alarm_autotest OK 1.17s
3/116 DPDK:fast-tests / argparse_autotest OK 0.18s
4/116 DPDK:fast-tests / atomic_autotest OK 0.37s
5/116 DPDK:fast-tests / bitcount_autotest OK 0.18s
6/116 DPDK:fast-tests / bitmap_autotest OK 0.17s
7/116 DPDK:fast-tests / bitops_autotest OK 1.67s
8/116 DPDK:fast-tests / bitratestats_autotest OK 0.17s
9/116 DPDK:fast-tests / bitset_autotest OK 1.34s
10/116 DPDK:fast-tests / bpf_autotest OK 0.18s
11/116 DPDK:fast-tests / bpf_convert_autotest OK 0.17s
12/116 DPDK:fast-tests / byteorder_autotest OK 0.17s
13/116 DPDK:fast-tests / cksum_autotest OK 0.17s
14/116 DPDK:fast-tests / cmdline_autotest OK 0.17s
15/116 DPDK:fast-tests / common_autotest OK 0.49s
16/116 DPDK:fast-tests / compressdev_autotest SKIP 0.14s exit status 77
17/116 DPDK:fast-tests / cpuflags_autotest OK 0.18s
18/116 DPDK:fast-tests / crc_autotest OK 0.17s
19/116 DPDK:fast-tests / user_delay_us OK 0.17s
20/116 DPDK:fast-tests / debug_autotest OK 0.47s
21/116 DPDK:fast-tests / devargs_autotest OK 0.18s
22/116 DPDK:fast-tests / dispatcher_autotest SKIP 0.14s exit status 77
23/116 DPDK:fast-tests / distributor_autotest OK 0.84s
24/116 DPDK:fast-tests / eal_flags_c_opt_autotest OK 0.76s
25/116 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.30s
26/116 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.47s
27/116 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.21s
28/116 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.49s
29/116 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.37s
30/116 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.31s
31/116 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.56s
32/116 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.26s
33/116 DPDK:fast-tests / eal_flags_mem_autotest OK 0.72s
34/116 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 3.37s
35/116 DPDK:fast-tests / eal_flags_misc_autotest OK 1.85s
36/116 DPDK:fast-tests / eal_fs_autotest OK 0.18s
37/116 DPDK:fast-tests / errno_autotest OK 0.18s
38/116 DPDK:fast-tests / ethdev_link_status OK 0.17s
39/116 DPDK:fast-tests / event_eth_tx_adapter_autotest FAIL 0.14s (exit status 255 or signal 127 SIGinvalid)
>>> MALLOC_PERTURB_=141 DPDK_TEST=event_eth_tx_adapter_autotest /home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/build/app/dpdk-test
40/116 DPDK:fast-tests / event_ring_autotest OK 0.18s
41/116 DPDK:fast-tests / eventdev_common_autotest OK 0.17s
42/116 DPDK:fast-tests / eventdev_selftest_sw OK 0.21s
43/116 DPDK:fast-tests / fbarray_autotest OK 0.17s
44/116 DPDK:fast-tests / fib_autotest OK 0.76s
45/116 DPDK:fast-tests / fib6_autotest OK 0.63s
46/116 DPDK:fast-tests / func_reentrancy_autotest OK 0.53s
47/116 DPDK:fast-tests / graph_autotest OK 0.18s
48/116 DPDK:fast-tests / node_list_dump OK 0.17s
49/116 DPDK:fast-tests / hash_autotest OK 0.28s
50/116 DPDK:fast-tests / hash_readwrite_func_autotest SKIP 0.14s exit status 77
51/116 DPDK:fast-tests / interrupt_autotest OK 1.19s
52/116 DPDK:fast-tests / ipfrag_autotest OK 0.15s
53/116 DPDK:fast-tests / ipsec_autotest SKIP 0.18s exit status 77
54/116 DPDK:fast-tests / kvargs_autotest OK 0.17s
55/116 DPDK:fast-tests / latencystats_autotest OK 0.17s
56/116 DPDK:fast-tests / lcores_autotest OK 0.74s
57/116 DPDK:fast-tests / logs_autotest OK 0.17s
58/116 DPDK:fast-tests / lpm_autotest OK 1.43s
59/116 DPDK:fast-tests / lpm6_autotest OK 2.62s
60/116 DPDK:fast-tests / malloc_autotest OK 0.99s
61/116 DPDK:fast-tests / mbuf_autotest OK 0.27s
62/116 DPDK:fast-tests / mcslock_autotest OK 0.47s
63/116 DPDK:fast-tests / member_autotest OK 0.78s
64/116 DPDK:fast-tests / memcpy_autotest OK 1.87s
65/116 DPDK:fast-tests / memory_autotest OK 0.14s
66/116 DPDK:fast-tests / mempool_autotest OK 0.43s
67/116 DPDK:fast-tests / memzone_autotest OK 0.15s
68/116 DPDK:fast-tests / meter_autotest OK 0.18s
69/116 DPDK:fast-tests / metrics_autotest OK 0.17s
70/116 DPDK:fast-tests / multiprocess_autotest OK 0.25s
71/116 DPDK:fast-tests / net_ether_autotest OK 0.49s
72/116 DPDK:fast-tests / net_ipv6_autotest OK 0.17s
73/116 DPDK:fast-tests / pcapng_autotest OK 5.89s
74/116 DPDK:fast-tests / pdcp_autotest SKIP 0.14s exit status 77
75/116 DPDK:fast-tests / pdump_autotest OK 0.29s
76/116 DPDK:fast-tests / per_lcore_autotest OK 0.28s
77/116 DPDK:fast-tests / pflock_autotest OK 0.28s
78/116 DPDK:fast-tests / pie_autotest OK 0.18s
79/116 DPDK:fast-tests / ring_pmd_autotest FAIL 0.18s (exit status 255 or signal 127 SIGinvalid)
>>> DPDK_TEST=ring_pmd_autotest MALLOC_PERTURB_=149 /home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/build/app/dpdk-test --no-huge -m 2048
80/116 DPDK:fast-tests / power_autotest OK 0.17s
81/116 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.14s exit status 77
82/116 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.18s exit status 77
83/116 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.14s exit status 77
84/116 DPDK:fast-tests / prefetch_autotest OK 0.18s
85/116 DPDK:fast-tests / ptr_compress_autotest OK 0.17s
86/116 DPDK:fast-tests / rawdev_autotest OK 0.17s
87/116 DPDK:fast-tests / rcu_qsbr_autotest OK 0.27s
88/116 DPDK:fast-tests / reorder_autotest OK 0.29s
89/116 DPDK:fast-tests / rib_autotest OK 3.85s
90/116 DPDK:fast-tests / rib6_autotest OK 3.42s
91/116 DPDK:fast-tests / ring_autotest OK 0.18s
92/116 DPDK:fast-tests / rwlock_test1_autotest OK 0.28s
93/116 DPDK:fast-tests / rwlock_rda_autotest OK 5.17s
94/116 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.17s
95/116 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.17s
96/116 DPDK:fast-tests / sched_autotest OK 0.18s
97/116 DPDK:fast-tests / security_autotest OK 0.14s
98/116 DPDK:fast-tests / seqlock_autotest SKIP 0.18s exit status 77
99/116 DPDK:fast-tests / service_autotest OK 0.27s
100/116 DPDK:fast-tests / spinlock_autotest OK 0.18s
101/116 DPDK:fast-tests / stack_autotest OK 0.18s
102/116 DPDK:fast-tests / stack_lf_autotest OK 0.22s
103/116 DPDK:fast-tests / string_autotest OK 0.18s
104/116 DPDK:fast-tests / table_autotest OK 4.93s
105/116 DPDK:fast-tests / tailq_autotest OK 0.17s
106/116 DPDK:fast-tests / telemetry_data_autotest OK 0.18s
107/116 DPDK:fast-tests / telemetry_json_autotest OK 0.17s
108/116 DPDK:fast-tests / thash_autotest OK 0.17s
109/116 DPDK:fast-tests / threads_autotest OK 0.32s
110/116 DPDK:fast-tests / ticketlock_autotest OK 0.18s
111/116 DPDK:fast-tests / timer_autotest OK 2.50s
112/116 DPDK:fast-tests / trace_autotest OK 0.21s
113/116 DPDK:fast-tests / trace_autotest_with_traces OK 0.18s
114/116 DPDK:fast-tests / vdev_autotest OK 0.17s
115/116 DPDK:fast-tests / version_autotest OK 0.18s
116/116 DPDK:fast-tests / telemetry_all SKIP 0.01s exit status 77
Ok: 104
Expected Fail: 0
Fail: 2
Unexpected Pass: 0
Skipped: 10
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 event_eth_tx_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.
Test log output from the failed test ring_pmd_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)
Fedora 40
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240801 (Red Hat 14.2.1-1)
RHEL8
Kernel: Depends on container host
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-22)
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 22.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Ubuntu 24.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31844/
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:[~2024-11-07 11:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241107092649.1507375-1-mb@smartsharesystems.com>
2024-11-07 8:55 ` |SUCCESS| pw148030 [TEST v11] ethdev: test single queue per port qemudev
2024-11-07 8:59 ` |FAILURE| " qemudev
2024-11-07 9:28 ` |WARNING| " checkpatch
2024-11-07 10:59 ` |FAILURE| pw148030 [PATCH] [TEST,v11] ethdev: test single queue per dpdklab
2024-11-07 11:06 ` |SUCCESS| " dpdklab
2024-11-07 11:08 ` dpdklab
2024-11-07 11:09 ` |FAILURE| " dpdklab
2024-11-07 11:16 ` |SUCCESS| " dpdklab
2024-11-07 11:19 ` dpdklab [this message]
2024-11-07 11:26 ` |FAILURE| " dpdklab
2024-11-07 11:39 ` |FAILURE| pw148030 [TEST v11] ethdev: test single queue per port 0-day Robot
2024-11-07 11:51 ` |PENDING| pw148030 [PATCH] [TEST,v11] ethdev: test single queue per dpdklab
2024-11-07 11:52 ` dpdklab
2024-11-07 11:54 ` |FAILURE| " dpdklab
2024-11-07 12:23 ` dpdklab
2024-11-07 12:25 ` dpdklab
2024-11-07 12:32 ` dpdklab
2024-11-07 12:36 ` |SUCCESS| " dpdklab
2024-11-07 12:42 ` |FAILURE| " dpdklab
2024-11-07 13:11 ` |SUCCESS| " dpdklab
2024-11-07 13:56 ` |FAILURE| " 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=672ca228.050a0220.2323a7.30d7SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=mb@smartsharesystems.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).