From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>, zhoumin@loongson.cn
Subject: |FAILURE| pw154231 [PATCH v18] trace: add PMU
Date: Tue, 10 Jun 2025 00:28:02 +0800 [thread overview]
Message-ID: <202506091628.559GS2jQ3854309@localhost.localdomain> (raw)
In-Reply-To: <20250609165736.2255515-1-thomas@monjalon.net>
Test-Label: loongarch-unit-testing
Test-Status: FAILURE
http://dpdk.org/patch/154231
_Unit Testing FAIL_
Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: Mon, 9 Jun 2025 18:55:24 +0200
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 1e648eee69c427a6b04a424b3d2f8ce27d9b15d0
154231 --> testing fail
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+---------------------+----------------+
| Loongnix-Server 8.3 | FAIL |
+---------------------+----------------+
Loongnix-Server 8.3
Kernel: 4.19.190+
Compiler: gcc 8.3
Test result details:
1/121 DPDK:fast-tests / acl_autotest OK 3.31s
2/121 DPDK:fast-tests / alarm_autotest OK 1.65s
3/121 DPDK:fast-tests / argparse_autotest OK 0.64s
4/121 DPDK:fast-tests / atomic_autotest OK 6.93s
5/121 DPDK:fast-tests / bitcount_autotest OK 0.31s
6/121 DPDK:fast-tests / bitmap_autotest OK 0.31s
7/121 DPDK:fast-tests / bitops_autotest OK 1.81s
8/121 DPDK:fast-tests / bitratestats_autotest OK 0.53s
9/121 DPDK:fast-tests / bitset_autotest OK 3.29s
10/121 DPDK:fast-tests / bpf_autotest OK 0.54s
11/121 DPDK:fast-tests / bpf_convert_autotest OK 0.53s
12/121 DPDK:fast-tests / byteorder_autotest OK 0.52s
13/121 DPDK:fast-tests / cfgfile_autotest OK 0.52s
14/121 DPDK:fast-tests / cksum_autotest OK 0.52s
15/121 DPDK:fast-tests / cmdline_autotest OK 0.52s
16/121 DPDK:fast-tests / common_autotest OK 1.40s
17/121 DPDK:fast-tests / compressdev_autotest SKIP 0.06s exit status 77
18/121 DPDK:fast-tests / cpuflags_autotest OK 0.43s
19/121 DPDK:fast-tests / crc_autotest OK 0.43s
20/121 DPDK:fast-tests / user_delay_us OK 0.43s
21/121 DPDK:fast-tests / debug_autotest OK 25.49s
22/121 DPDK:fast-tests / devargs_autotest OK 0.43s
23/121 DPDK:fast-tests / dispatcher_autotest OK 2.47s
24/121 DPDK:fast-tests / distributor_autotest OK 1.20s
25/121 DPDK:fast-tests / eal_flags_c_opt_autotest OK 0.80s
26/121 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.22s
27/121 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.20s
28/121 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.13s
29/121 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.22s
30/121 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.30s
31/121 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.25s
32/121 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.20s
33/121 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.19s
34/121 DPDK:fast-tests / eal_flags_mem_autotest OK 0.60s
35/121 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 22.26s
36/121 DPDK:fast-tests / eal_flags_misc_autotest OK 1.06s
37/121 DPDK:fast-tests / eal_fs_autotest OK 0.43s
38/121 DPDK:fast-tests / errno_autotest OK 0.43s
39/121 DPDK:fast-tests / ethdev_link_status OK 0.43s
40/121 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.69s
41/121 DPDK:fast-tests / event_ring_autotest OK 0.43s
42/121 DPDK:fast-tests / event_vector_adapter_autotest FAIL 2.50s exit status 255
43/121 DPDK:fast-tests / eventdev_common_autotest OK 0.43s
44/121 DPDK:fast-tests / eventdev_selftest_sw OK 7.28s
45/121 DPDK:fast-tests / fbarray_autotest OK 0.43s
46/121 DPDK:fast-tests / fib_autotest OK 1.27s
47/121 DPDK:fast-tests / fib6_autotest OK 1.06s
48/121 DPDK:fast-tests / func_reentrancy_autotest OK 2.33s
49/121 DPDK:fast-tests / graph_autotest OK 0.43s
50/121 DPDK:fast-tests / node_list_dump OK 0.43s
51/121 DPDK:fast-tests / hash_autotest OK 1.05s
52/121 DPDK:fast-tests / hash_readwrite_func_autotest OK 6.39s
53/121 DPDK:fast-tests / interrupt_autotest OK 1.63s
54/121 DPDK:fast-tests / ipfrag_autotest OK 0.07s
55/121 DPDK:fast-tests / ipsec_autotest SKIP 0.43s exit status 77
56/121 DPDK:fast-tests / kvargs_autotest OK 0.44s
57/121 DPDK:fast-tests / latencystats_autotest OK 0.44s
58/121 DPDK:fast-tests / lcore_var_autotest OK 0.57s
59/121 DPDK:fast-tests / lcores_autotest OK 5.24s
60/121 DPDK:fast-tests / logs_autotest OK 0.53s
61/121 DPDK:fast-tests / lpm_autotest OK 2.48s
62/121 DPDK:fast-tests / lpm6_autotest OK 5.64s
63/121 DPDK:fast-tests / malloc_autotest OK 59.31s
64/121 DPDK:fast-tests / mbuf_autotest OK 5.26s
65/121 DPDK:fast-tests / mcslock_autotest OK 3.03s
66/121 DPDK:fast-tests / member_autotest OK 1.59s
67/121 DPDK:fast-tests / memcpy_autotest OK 6.86s
68/121 DPDK:fast-tests / memory_autotest OK 0.10s
69/121 DPDK:fast-tests / mempool_autotest OK 0.43s
70/121 DPDK:fast-tests / memzone_autotest OK 0.14s
71/121 DPDK:fast-tests / meter_autotest OK 0.42s
72/121 DPDK:fast-tests / metrics_autotest OK 0.43s
73/121 DPDK:fast-tests / multiprocess_autotest OK 0.19s
74/121 DPDK:fast-tests / net_ether_autotest OK 1.09s
75/121 DPDK:fast-tests / net_ipv6_autotest OK 0.43s
76/121 DPDK:fast-tests / pcapng_autotest OK 6.84s
77/121 DPDK:fast-tests / pdcp_autotest SKIP 0.07s exit status 77
78/121 DPDK:fast-tests / pdump_autotest OK 0.55s
79/121 DPDK:fast-tests / per_lcore_autotest OK 0.53s
80/121 DPDK:fast-tests / pflock_autotest OK 1.24s
81/121 DPDK:fast-tests / pie_autotest OK 0.43s
82/121 DPDK:fast-tests / ring_pmd_autotest OK 0.43s
83/121 DPDK:fast-tests / pmu_autotest SKIP 0.53s exit status 77
84/121 DPDK:fast-tests / power_autotest OK 0.43s
85/121 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.07s exit status 77
86/121 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.42s exit status 77
87/121 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.07s exit status 77
88/121 DPDK:fast-tests / prefetch_autotest OK 0.42s
89/121 DPDK:fast-tests / ptr_compress_autotest OK 0.43s
90/121 DPDK:fast-tests / rawdev_autotest OK 0.43s
91/121 DPDK:fast-tests / rcu_qsbr_autotest OK 0.95s
92/121 DPDK:fast-tests / reorder_autotest OK 0.59s
93/121 DPDK:fast-tests / rib_autotest OK 9.07s
94/121 DPDK:fast-tests / rib6_autotest OK 9.06s
95/121 DPDK:fast-tests / ring_autotest OK 0.45s
96/121 DPDK:fast-tests / rwlock_test1_autotest OK 1.18s
97/121 DPDK:fast-tests / rwlock_rda_autotest OK 5.43s
98/121 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.43s
99/121 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.43s
100/121 DPDK:fast-tests / sched_autotest OK 0.43s
101/121 DPDK:fast-tests / security_autotest OK 0.07s
102/121 DPDK:fast-tests / seqlock_autotest OK 2.42s
103/121 DPDK:fast-tests / service_autotest OK 3.13s
104/121 DPDK:fast-tests / soring_autotest OK 0.53s
105/121 DPDK:fast-tests / spinlock_autotest OK 0.51s
106/121 DPDK:fast-tests / stack_autotest OK 0.86s
107/121 DPDK:fast-tests / stack_lf_autotest SKIP 0.06s exit status 77
108/121 DPDK:fast-tests / string_autotest OK 0.42s
109/121 DPDK:fast-tests / table_autotest OK 7.80s
110/121 DPDK:fast-tests / tailq_autotest OK 0.42s
111/121 DPDK:fast-tests / telemetry_data_autotest OK 0.43s
112/121 DPDK:fast-tests / telemetry_json_autotest OK 0.43s
113/121 DPDK:fast-tests / thash_autotest OK 0.44s
114/121 DPDK:fast-tests / threads_autotest OK 0.60s
115/121 DPDK:fast-tests / ticketlock_autotest OK 0.61s
116/121 DPDK:fast-tests / timer_autotest OK 3.96s
117/121 DPDK:fast-tests / trace_autotest OK 0.42s
118/121 DPDK:fast-tests / trace_autotest_with_traces OK 0.43s
119/121 DPDK:fast-tests / vdev_autotest OK 0.42s
120/121 DPDK:fast-tests / version_autotest OK 0.43s
121/121 DPDK:fast-tests / telemetry_all OK 1.36s
Ok: 112
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 8
Timeout: 0
Test logs for failed test cases:
================================================================================
DPDK:fast-tests / event_vector_adapter_autotest: FAIL
================================================================================
-------------------------------------stdout-------------------------------------
RTE>>event_vector_adapter_autotest
+ ------------------------------------------------------- +
+ Test Suite : Event vector adapter test suite
+ ------------------------------------------------------- +
+ TestCase [ 0] : test_event_vector_adapter_create succeeded
+ TestCase [ 1] : test_event_vector_adapter_create_multi succeeded
+ TestCase [ 2] : test_event_vector_adapter_enqueue succeeded
+ TestCase [ 3] : test_event_vector_adapter_enqueue_tmo failed
+ TestCase [ 4] : test_event_vector_adapter_enqueue_fallback succeeded
+ TestCase [ 5] : test_event_vector_adapter_enqueue_sov succeeded
+ TestCase [ 6] : test_event_vector_adapter_enqueue_eov succeeded
+ TestCase [ 7] : test_event_vector_adapter_enqueue_sov_eov succeeded
+ TestCase [ 8] : test_event_vector_adapter_enqueue_flush succeeded
+ ------------------------------------------------------- +
+ Test Suite Summary : Event vector adapter test suite
+ ------------------------------------------------------- +
+ Tests Total : 9
+ Tests Skipped : 0
+ Tests Executed : 9
+ Tests Unsupported: 0
+ Tests Passed : 8
+ Tests Failed : 1
+ ------------------------------------------------------- +
Test Failed
RTE>>
-------------------------------------stderr-------------------------------------
EAL: Detected CPU lcores: 32
EAL: Detected NUMA nodes: 8
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
APP: HPET is not enabled, using TSC as default timer
EAL: Test assert test_event_vector_adapter_enqueue_tmo line 248 failed: Failed to dequeue event vector 0
next prev parent reply other threads:[~2025-06-09 17:04 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250609165736.2255515-1-thomas@monjalon.net>
2025-06-09 16:23 ` |SUCCESS| " qemudev
2025-06-09 16:28 ` qemudev [this message]
2025-06-09 16:57 ` checkpatch
2025-06-09 17:24 ` |FAILURE| " 0-day Robot
2025-06-09 22:04 ` |FAILURE| pw154231 [PATCH] [v18] " dpdklab
2025-06-09 22:05 ` dpdklab
2025-06-09 22:10 ` |SUCCESS| " dpdklab
2025-06-09 22:12 ` dpdklab
2025-06-09 22:18 ` |FAILURE| " dpdklab
2025-06-09 22:34 ` |PENDING| " dpdklab
2025-06-09 22:37 ` |FAILURE| " dpdklab
2025-06-09 22:40 ` dpdklab
2025-06-09 23:04 ` |SUCCESS| " dpdklab
2025-06-09 23:48 ` |FAILURE| " dpdklab
2025-06-10 0:19 ` |WARNING| " dpdklab
2025-06-10 0:20 ` |FAILURE| " dpdklab
2025-06-10 0:21 ` dpdklab
2025-06-10 0:22 ` dpdklab
2025-06-10 0:23 ` dpdklab
2025-06-10 0:51 ` |WARNING| " dpdklab
2025-06-10 3:02 ` |FAILURE| " dpdklab
2025-06-10 3:12 ` dpdklab
2025-06-10 3:16 ` dpdklab
2025-06-10 3:26 ` dpdklab
2025-06-10 4:52 ` dpdklab
2025-06-10 4:53 ` dpdklab
2025-06-10 4:53 ` dpdklab
2025-06-10 4:53 ` dpdklab
2025-06-10 7:59 ` |WARNING| " dpdklab
2025-06-10 8:13 ` |FAILURE| " dpdklab
2025-06-10 8:14 ` dpdklab
2025-06-10 8:15 ` dpdklab
2025-06-10 8:16 ` dpdklab
2025-06-10 8:17 ` dpdklab
2025-06-10 8:18 ` dpdklab
2025-06-10 8:18 ` dpdklab
2025-06-10 8:19 ` dpdklab
2025-06-10 8:21 ` dpdklab
2025-06-10 8:23 ` |WARNING| " dpdklab
2025-06-10 8:23 ` dpdklab
2025-06-10 8:24 ` dpdklab
2025-06-10 20:26 ` |SUCCESS| " dpdklab
2025-06-10 20:26 ` |WARNING| " 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=202506091628.559GS2jQ3854309@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
--cc=zhoumin@loongson.cn \
/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).