From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Dengdui Huang <huangdengdui@huawei.com>, zhoumin@loongson.cn
Subject: |FAILURE| pw152595-152596 [PATCH v2 2/2] app/dma-perf: fix infinite loop
Date: Thu, 27 Mar 2025 17:03:51 +0800 [thread overview]
Message-ID: <202503270903.52R93pRq3306367@localhost.localdomain> (raw)
In-Reply-To: <20250327090116.3357137-3-huangdengdui@huawei.com>
Test-Label: loongarch-unit-testing
Test-Status: FAILURE
http://dpdk.org/patch/152596
_Unit Testing FAIL_
Submitter: Dengdui Huang <huangdengdui@huawei.com>
Date: Thu, 27 Mar 2025 17:01:15 +0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: edd3f4b1265e6da707c46ca9b6c39d332647baea
152595-152596 --> 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/119 DPDK:fast-tests / acl_autotest OK 3.31s
2/119 DPDK:fast-tests / alarm_autotest OK 1.54s
3/119 DPDK:fast-tests / argparse_autotest OK 0.53s
4/119 DPDK:fast-tests / atomic_autotest OK 6.90s
5/119 DPDK:fast-tests / bitcount_autotest OK 0.40s
6/119 DPDK:fast-tests / bitmap_autotest OK 0.49s
7/119 DPDK:fast-tests / bitops_autotest OK 1.90s
8/119 DPDK:fast-tests / bitratestats_autotest OK 0.40s
9/119 DPDK:fast-tests / bitset_autotest OK 3.11s
10/119 DPDK:fast-tests / bpf_autotest OK 0.40s
11/119 DPDK:fast-tests / bpf_convert_autotest OK 0.40s
12/119 DPDK:fast-tests / byteorder_autotest OK 0.40s
13/119 DPDK:fast-tests / cfgfile_autotest OK 0.40s
14/119 DPDK:fast-tests / cksum_autotest OK 0.40s
15/119 DPDK:fast-tests / cmdline_autotest OK 0.40s
16/119 DPDK:fast-tests / common_autotest OK 1.28s
17/119 DPDK:fast-tests / compressdev_autotest SKIP 0.06s exit status 77
18/119 DPDK:fast-tests / cpuflags_autotest OK 0.39s
19/119 DPDK:fast-tests / crc_autotest OK 0.40s
20/119 DPDK:fast-tests / user_delay_us OK 0.40s
21/119 DPDK:fast-tests / debug_autotest OK 27.19s
22/119 DPDK:fast-tests / devargs_autotest OK 0.39s
23/119 DPDK:fast-tests / dispatcher_autotest FAIL 0.08s exit status 255
24/119 DPDK:fast-tests / distributor_autotest OK 1.20s
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.22s
27/119 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.20s
28/119 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.13s
29/119 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.22s
30/119 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.30s
31/119 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.25s
32/119 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.19s
33/119 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.19s
34/119 DPDK:fast-tests / eal_flags_mem_autotest OK 0.59s
35/119 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 22.25s
36/119 DPDK:fast-tests / eal_flags_misc_autotest OK 1.05s
37/119 DPDK:fast-tests / eal_fs_autotest OK 0.39s
38/119 DPDK:fast-tests / errno_autotest OK 0.40s
39/119 DPDK:fast-tests / ethdev_link_status OK 0.39s
40/119 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.68s
41/119 DPDK:fast-tests / event_ring_autotest OK 0.40s
42/119 DPDK:fast-tests / eventdev_common_autotest OK 0.40s
43/119 DPDK:fast-tests / eventdev_selftest_sw OK 7.18s
44/119 DPDK:fast-tests / fbarray_autotest OK 0.40s
45/119 DPDK:fast-tests / fib_autotest OK 1.28s
46/119 DPDK:fast-tests / fib6_autotest OK 1.06s
47/119 DPDK:fast-tests / func_reentrancy_autotest OK 2.25s
48/119 DPDK:fast-tests / graph_autotest OK 0.43s
49/119 DPDK:fast-tests / node_list_dump OK 0.40s
50/119 DPDK:fast-tests / hash_autotest OK 1.02s
51/119 DPDK:fast-tests / hash_readwrite_func_autotest OK 6.39s
52/119 DPDK:fast-tests / interrupt_autotest OK 1.70s
53/119 DPDK:fast-tests / ipfrag_autotest OK 0.07s
54/119 DPDK:fast-tests / ipsec_autotest SKIP 0.40s exit status 77
55/119 DPDK:fast-tests / kvargs_autotest OK 0.40s
56/119 DPDK:fast-tests / latencystats_autotest OK 0.40s
57/119 DPDK:fast-tests / lcore_var_autotest OK 0.53s
58/119 DPDK:fast-tests / lcores_autotest OK 5.20s
59/119 DPDK:fast-tests / logs_autotest OK 0.39s
60/119 DPDK:fast-tests / lpm_autotest OK 2.45s
61/119 DPDK:fast-tests / lpm6_autotest OK 5.54s
62/119 DPDK:fast-tests / malloc_autotest OK 60.63s
63/119 DPDK:fast-tests / mbuf_autotest OK 5.16s
64/119 DPDK:fast-tests / mcslock_autotest OK 3.12s
65/119 DPDK:fast-tests / member_autotest OK 1.57s
66/119 DPDK:fast-tests / memcpy_autotest OK 6.97s
67/119 DPDK:fast-tests / memory_autotest OK 0.08s
68/119 DPDK:fast-tests / mempool_autotest OK 0.43s
69/119 DPDK:fast-tests / memzone_autotest OK 0.14s
70/119 DPDK:fast-tests / meter_autotest OK 0.39s
71/119 DPDK:fast-tests / metrics_autotest OK 0.40s
72/119 DPDK:fast-tests / multiprocess_autotest OK 0.18s
73/119 DPDK:fast-tests / net_ether_autotest OK 1.06s
74/119 DPDK:fast-tests / net_ipv6_autotest OK 0.40s
75/119 DPDK:fast-tests / pcapng_autotest OK 7.23s
76/119 DPDK:fast-tests / pdcp_autotest SKIP 0.07s exit status 77
77/119 DPDK:fast-tests / pdump_autotest OK 0.50s
78/119 DPDK:fast-tests / per_lcore_autotest OK 0.50s
79/119 DPDK:fast-tests / pflock_autotest OK 1.20s
80/119 DPDK:fast-tests / pie_autotest OK 0.40s
81/119 DPDK:fast-tests / ring_pmd_autotest OK 0.40s
82/119 DPDK:fast-tests / power_autotest OK 0.40s
83/119 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.07s exit status 77
84/119 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.39s exit status 77
85/119 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.07s exit status 77
86/119 DPDK:fast-tests / prefetch_autotest OK 0.39s
87/119 DPDK:fast-tests / ptr_compress_autotest OK 0.40s
88/119 DPDK:fast-tests / rawdev_autotest OK 0.39s
89/119 DPDK:fast-tests / rcu_qsbr_autotest OK 0.92s
90/119 DPDK:fast-tests / reorder_autotest OK 0.45s
91/119 DPDK:fast-tests / rib_autotest OK 9.05s
92/119 DPDK:fast-tests / rib6_autotest OK 9.04s
93/119 DPDK:fast-tests / ring_autotest OK 0.42s
94/119 DPDK:fast-tests / rwlock_test1_autotest OK 1.14s
95/119 DPDK:fast-tests / rwlock_rda_autotest OK 5.40s
96/119 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.37s
97/119 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.40s
98/119 DPDK:fast-tests / sched_autotest OK 0.40s
99/119 DPDK:fast-tests / security_autotest OK 0.07s
100/119 DPDK:fast-tests / seqlock_autotest OK 2.39s
101/119 DPDK:fast-tests / service_autotest FAIL 2.40s exit status 255
102/119 DPDK:fast-tests / soring_autotest OK 0.40s
103/119 DPDK:fast-tests / spinlock_autotest OK 0.47s
104/119 DPDK:fast-tests / stack_autotest OK 0.87s
105/119 DPDK:fast-tests / stack_lf_autotest SKIP 0.06s exit status 77
106/119 DPDK:fast-tests / string_autotest OK 0.39s
107/119 DPDK:fast-tests / table_autotest OK 7.50s
108/119 DPDK:fast-tests / tailq_autotest OK 0.39s
109/119 DPDK:fast-tests / telemetry_data_autotest OK 0.40s
110/119 DPDK:fast-tests / telemetry_json_autotest OK 0.40s
111/119 DPDK:fast-tests / thash_autotest OK 0.41s
112/119 DPDK:fast-tests / threads_autotest OK 0.57s
113/119 DPDK:fast-tests / ticketlock_autotest OK 0.55s
114/119 DPDK:fast-tests / timer_autotest OK 3.88s
115/119 DPDK:fast-tests / trace_autotest OK 0.39s
116/119 DPDK:fast-tests / trace_autotest_with_traces OK 0.40s
117/119 DPDK:fast-tests / vdev_autotest OK 0.39s
118/119 DPDK:fast-tests / version_autotest OK 0.39s
119/119 DPDK:fast-tests / telemetry_all OK 1.32s
Ok: 110
Expected Fail: 0
Fail: 2
Unexpected Pass: 0
Skipped: 7
Timeout: 0
Test logs for failed test cases:
================================================================================
DPDK:fast-tests / dispatcher_autotest: FAIL
================================================================================
-------------------------------------stdout-------------------------------------
RTE>>dispatcher_autotest
+ ------------------------------------------------------- +
+ Test Suite : Event dispatcher test suite
+ ------------------------------------------------------- +
+ TestCase [ 0] : test_basic failed
+ TestCase [ 1] : test_drop skipped
+ TestCase [ 2] : test_many_handler_registrations skipped
+ TestCase [ 3] : test_many_finalize_registrations skipped
+ ------------------------------------------------------- +
+ Test Suite Summary : Event dispatcher test suite
+ ------------------------------------------------------- +
+ Tests Total : 4
+ Tests Skipped : 3
+ Tests Executed : 4
+ Tests Unsupported: 0
+ Tests Passed : 0
+ 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 'PA'
APP: HPET is not enabled, using TSC as default timer
EAL: Test assert test_app_start_service_cores line 643 failed: Unable to start service lcore 1
EAL: Test assert test_app_teardown_service_core line 610 failed: Unable change role of service lcore 1
EVENTDEV: rte_event_dev_close() line 1550: Device 0 must be stopped before closing
EAL: Test assert test_app_destroy_vdev line 114 failed: Error while closing event device
EVENTDEV: rte_event_dev_close() line 1550: Device 0 must be stopped before closing
================================================================================
DPDK:fast-tests / service_autotest: FAIL
================================================================================
-------------------------------------stdout-------------------------------------
RTE>>service_autotest
+ ------------------------------------------------------- +
+ Test Suite : service core test suite
+ ------------------------------------------------------- +
+ TestCase [ 0] : unregister_all succeeded
+ TestCase [ 1] : service_name succeeded
+ TestCase [ 2] : service_get_by_name succeeded
Service dummy_service Summary
dummy_service: stats 1 calls 1 cycles 0 avg: 0
Service dummy_service Summary
dummy_service: stats 0 calls 1 cycles 0 avg: 0
+ TestCase [ 3] : service_dump succeeded
+ TestCase [ 4] : service_probe_capability succeeded
+ TestCase [ 5] : service_start_stop succeeded
+ TestCase [ 6] : service_lcore_add_del succeeded
+ TestCase [ 7] : service_lcore_en_dis_able failed
+ TestCase [ 8] : service_mt_unsafe_poll succeeded
+ TestCase [ 9] : service_mt_safe_poll failed
+ TestCase [10] : service_may_be_active failed
+ TestCase [11] : service_active_two_cores failed
+ ------------------------------------------------------- +
+ Test Suite Summary : service core test suite
+ ------------------------------------------------------- +
+ Tests Total : 12
+ Tests Skipped : 0
+ Tests Executed : 12
+ Tests Unsupported: 0
+ Tests Passed : 8
+ Tests Failed : 4
+ ------------------------------------------------------- +
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 service_lcore_en_dis_able line 567 failed: Ex-service core remote launch failed.
EAL: Test assert service_threaded_test line 737 failed: MT Safe service not run by two cores concurrently
EAL: Test assert service_mt_safe_poll line 762 failed: Error: MT Safe service not run by two cores concurrently
EAL: Test assert service_may_be_active line 997 failed: Service core start after add failed
EAL: Test assert service_active_two_cores line 1037 failed: Service core start after add failed
next prev parent reply other threads:[~2025-03-27 9:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250327090116.3357137-3-huangdengdui@huawei.com>
2025-03-27 8:59 ` |SUCCESS| " qemudev
2025-03-27 9:01 ` |SUCCESS| pw152596 " checkpatch
2025-03-27 9:03 ` qemudev [this message]
2025-03-27 10:22 ` |FAILURE| " 0-day Robot
2025-03-27 13:08 ` |SUCCESS| pw152595-152596 [PATCH] [v2,2/2] app/dma-perf: fix infinit dpdklab
2025-03-27 13:14 ` dpdklab
2025-03-27 13:14 ` dpdklab
2025-03-27 13:14 ` dpdklab
2025-03-27 13:18 ` |PENDING| " dpdklab
2025-03-27 13:18 ` |FAILURE| " dpdklab
2025-03-27 13:26 ` |SUCCESS| " dpdklab
2025-03-27 13:27 ` dpdklab
2025-03-27 13:29 ` dpdklab
2025-03-27 13:48 ` |FAILURE| " dpdklab
2025-03-27 13:58 ` |PENDING| " dpdklab
2025-03-27 14:00 ` |FAILURE| " dpdklab
2025-03-27 14:09 ` |SUCCESS| " dpdklab
2025-03-27 14:21 ` dpdklab
2025-03-27 14:34 ` dpdklab
2025-03-27 15:28 ` dpdklab
2025-03-27 15:30 ` dpdklab
2025-03-27 21:16 ` dpdklab
2025-03-27 21:31 ` dpdklab
2025-03-28 20:14 ` dpdklab
2025-03-29 2:12 ` 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=202503270903.52R93pRq3306367@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=huangdengdui@huawei.com \
--cc=test-report@dpdk.org \
--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).