From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Robin Jarry <rjarry@redhat.com>, zhoumin@loongson.cn
Subject: |FAILURE| pw154285 [RFC PATCH dpdk] fib6: implement RCU rule reclamation
Date: Tue, 10 Jun 2025 22:29:45 +0800 [thread overview]
Message-ID: <202506101429.55AETjCn224916@localhost.localdomain> (raw)
In-Reply-To: <20250610145341.38271-2-rjarry@redhat.com>
Test-Label: loongarch-unit-testing
Test-Status: FAILURE
http://dpdk.org/patch/154285
_Unit Testing FAIL_
Submitter: Robin Jarry <rjarry@redhat.com>
Date: Tue, 10 Jun 2025 16:53:42 +0200
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: fbecf790b603cccac6eeda4536cba3e043ade209
154285 --> 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/120 DPDK:fast-tests / acl_autotest OK 3.18s
2/120 DPDK:fast-tests / alarm_autotest OK 1.35s
3/120 DPDK:fast-tests / argparse_autotest OK 0.34s
4/120 DPDK:fast-tests / atomic_autotest OK 6.90s
5/120 DPDK:fast-tests / bitcount_autotest OK 0.20s
6/120 DPDK:fast-tests / bitmap_autotest OK 0.20s
7/120 DPDK:fast-tests / bitops_autotest OK 1.70s
8/120 DPDK:fast-tests / bitratestats_autotest OK 0.20s
9/120 DPDK:fast-tests / bitset_autotest OK 2.95s
10/120 DPDK:fast-tests / bpf_autotest OK 0.20s
11/120 DPDK:fast-tests / bpf_convert_autotest OK 0.21s
12/120 DPDK:fast-tests / byteorder_autotest OK 0.20s
13/120 DPDK:fast-tests / cfgfile_autotest OK 0.20s
14/120 DPDK:fast-tests / cksum_autotest OK 0.20s
15/120 DPDK:fast-tests / cmdline_autotest OK 0.20s
16/120 DPDK:fast-tests / common_autotest OK 1.08s
17/120 DPDK:fast-tests / compressdev_autotest SKIP 0.06s exit status 77
18/120 DPDK:fast-tests / cpuflags_autotest OK 0.20s
19/120 DPDK:fast-tests / crc_autotest OK 0.20s
20/120 DPDK:fast-tests / user_delay_us OK 0.20s
21/120 DPDK:fast-tests / debug_autotest OK 22.97s
22/120 DPDK:fast-tests / devargs_autotest OK 0.31s
23/120 DPDK:fast-tests / dispatcher_autotest OK 2.48s
24/120 DPDK:fast-tests / distributor_autotest OK 1.20s
25/120 DPDK:fast-tests / eal_flags_c_opt_autotest OK 0.83s
26/120 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.22s
27/120 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.20s
28/120 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.13s
29/120 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.23s
30/120 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.31s
31/120 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.25s
32/120 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.20s
33/120 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.19s
34/120 DPDK:fast-tests / eal_flags_mem_autotest OK 0.61s
35/120 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 22.23s
36/120 DPDK:fast-tests / eal_flags_misc_autotest OK 1.09s
37/120 DPDK:fast-tests / eal_fs_autotest OK 0.20s
38/120 DPDK:fast-tests / errno_autotest OK 0.20s
39/120 DPDK:fast-tests / ethdev_link_status OK 0.20s
40/120 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.68s
41/120 DPDK:fast-tests / event_ring_autotest OK 0.21s
42/120 DPDK:fast-tests / event_vector_adapter_autotest OK 2.25s
43/120 DPDK:fast-tests / eventdev_common_autotest OK 0.20s
44/120 DPDK:fast-tests / eventdev_selftest_sw OK 6.95s
45/120 DPDK:fast-tests / fbarray_autotest OK 0.21s
46/120 DPDK:fast-tests / fib_autotest OK 1.07s
47/120 DPDK:fast-tests / fib6_autotest FAIL 1.06s exit status 255
48/120 DPDK:fast-tests / func_reentrancy_autotest OK 2.37s
49/120 DPDK:fast-tests / graph_autotest OK 0.21s
50/120 DPDK:fast-tests / node_list_dump OK 0.20s
51/120 DPDK:fast-tests / hash_autotest OK 0.83s
52/120 DPDK:fast-tests / hash_readwrite_func_autotest OK 6.36s
53/120 DPDK:fast-tests / interrupt_autotest OK 1.51s
54/120 DPDK:fast-tests / ipfrag_autotest OK 0.07s
55/120 DPDK:fast-tests / ipsec_autotest SKIP 0.21s exit status 77
56/120 DPDK:fast-tests / kvargs_autotest OK 0.21s
57/120 DPDK:fast-tests / latencystats_autotest OK 0.21s
58/120 DPDK:fast-tests / lcore_var_autotest OK 0.35s
59/120 DPDK:fast-tests / lcores_autotest OK 5.01s
60/120 DPDK:fast-tests / logs_autotest OK 0.20s
61/120 DPDK:fast-tests / lpm_autotest OK 2.27s
62/120 DPDK:fast-tests / lpm6_autotest OK 5.34s
63/120 DPDK:fast-tests / malloc_autotest OK 62.80s
64/120 DPDK:fast-tests / mbuf_autotest OK 4.86s
65/120 DPDK:fast-tests / mcslock_autotest OK 4.25s
66/120 DPDK:fast-tests / member_autotest OK 1.41s
67/120 DPDK:fast-tests / memcpy_autotest OK 6.82s
68/120 DPDK:fast-tests / memory_autotest OK 0.08s
69/120 DPDK:fast-tests / mempool_autotest OK 0.43s
70/120 DPDK:fast-tests / memzone_autotest OK 0.14s
71/120 DPDK:fast-tests / meter_autotest OK 0.20s
72/120 DPDK:fast-tests / metrics_autotest OK 0.20s
73/120 DPDK:fast-tests / multiprocess_autotest OK 0.18s
74/120 DPDK:fast-tests / net_ether_autotest OK 0.86s
75/120 DPDK:fast-tests / net_ipv6_autotest OK 0.20s
76/120 DPDK:fast-tests / pcapng_autotest OK 6.47s
77/120 DPDK:fast-tests / pdcp_autotest SKIP 0.06s exit status 77
78/120 DPDK:fast-tests / pdump_autotest OK 0.31s
79/120 DPDK:fast-tests / per_lcore_autotest OK 0.30s
80/120 DPDK:fast-tests / pflock_autotest OK 1.01s
81/120 DPDK:fast-tests / pie_autotest OK 0.20s
82/120 DPDK:fast-tests / ring_pmd_autotest OK 0.20s
83/120 DPDK:fast-tests / power_autotest OK 0.20s
84/120 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.06s exit status 77
85/120 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.20s exit status 77
86/120 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.06s exit status 77
87/120 DPDK:fast-tests / prefetch_autotest OK 0.20s
88/120 DPDK:fast-tests / ptr_compress_autotest OK 0.20s
89/120 DPDK:fast-tests / rawdev_autotest OK 0.20s
90/120 DPDK:fast-tests / rcu_qsbr_autotest OK 0.72s
91/120 DPDK:fast-tests / reorder_autotest OK 0.26s
92/120 DPDK:fast-tests / rib_autotest OK 8.86s
93/120 DPDK:fast-tests / rib6_autotest OK 8.84s
94/120 DPDK:fast-tests / ring_autotest OK 0.23s
95/120 DPDK:fast-tests / rwlock_test1_autotest OK 0.95s
96/120 DPDK:fast-tests / rwlock_rda_autotest OK 5.20s
97/120 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.20s
98/120 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.20s
99/120 DPDK:fast-tests / sched_autotest OK 0.20s
100/120 DPDK:fast-tests / security_autotest OK 0.06s
101/120 DPDK:fast-tests / seqlock_autotest OK 2.21s
102/120 DPDK:fast-tests / service_autotest OK 2.90s
103/120 DPDK:fast-tests / soring_autotest OK 0.43s
104/120 DPDK:fast-tests / spinlock_autotest OK 0.51s
105/120 DPDK:fast-tests / stack_autotest OK 0.86s
106/120 DPDK:fast-tests / stack_lf_autotest SKIP 0.06s exit status 77
107/120 DPDK:fast-tests / string_autotest OK 0.39s
108/120 DPDK:fast-tests / table_autotest OK 7.74s
109/120 DPDK:fast-tests / tailq_autotest OK 0.39s
110/120 DPDK:fast-tests / telemetry_data_autotest OK 0.40s
111/120 DPDK:fast-tests / telemetry_json_autotest OK 0.40s
112/120 DPDK:fast-tests / thash_autotest OK 0.41s
113/120 DPDK:fast-tests / threads_autotest OK 0.58s
114/120 DPDK:fast-tests / ticketlock_autotest OK 0.57s
115/120 DPDK:fast-tests / timer_autotest OK 3.89s
116/120 DPDK:fast-tests / trace_autotest OK 0.39s
117/120 DPDK:fast-tests / trace_autotest_with_traces OK 0.40s
118/120 DPDK:fast-tests / vdev_autotest OK 0.39s
119/120 DPDK:fast-tests / version_autotest OK 0.40s
120/120 DPDK:fast-tests / telemetry_all OK 1.32s
Ok: 112
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 7
Timeout: 0
Test logs for failed test cases:
================================================================================
DPDK:fast-tests / fib6_autotest: FAIL
================================================================================
-------------------------------------stdout-------------------------------------
RTE>>fib6_autotest
+ ------------------------------------------------------- +
+ Test Suite : fib6 autotest
+ ------------------------------------------------------- +
+ TestCase [ 0] : test_create_invalid succeeded
+ TestCase [ 1] : test_free_null succeeded
+ TestCase [ 2] : test_add_del_invalid succeeded
+ TestCase [ 3] : test_get_invalid succeeded
+ TestCase [ 4] : test_lookup succeeded
+ TestCase [ 5] : test_invalid_rcu succeeded
test_fib_rcu_sync_rw: Failed to add rule
+ TestCase [ 6] : test_fib_rcu_sync_rw failed
+ ------------------------------------------------------- +
+ Test Suite Summary : fib6 autotest
+ ------------------------------------------------------- +
+ Tests Total : 7
+ Tests Skipped : 0
+ Tests Executed : 7
+ Tests Unsupported: 0
+ Tests Passed : 6
+ 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
RIB: Can not allocate mempool for RIB6 test_create_invalid
FIB: Can not allocate RIB test_create_invalid
FIB: Can not allocate RIB test_create_invalid
FIB: FIB dataplane struct test_create_invalid memory allocation failed
FIB: FIB dataplane struct test_create_invalid memory allocation failed
next prev parent reply other threads:[~2025-06-10 15:06 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250610145341.38271-2-rjarry@redhat.com>
2025-06-10 14:25 ` |SUCCESS| " qemudev
2025-06-10 14:29 ` qemudev [this message]
2025-06-10 14:54 ` |WARNING| " checkpatch
2025-06-10 16:04 ` |FAILURE| " 0-day Robot
2025-06-10 18:04 ` |SUCCESS| pw154285 [PATCH] [RFC] fib6: implement RCU rule reclamatio dpdklab
2025-06-10 18:06 ` dpdklab
2025-06-10 18:21 ` dpdklab
2025-06-10 18:36 ` |PENDING| " dpdklab
2025-06-10 18:54 ` |WARNING| " dpdklab
2025-06-10 19:02 ` dpdklab
2025-06-10 19:23 ` |SUCCESS| " dpdklab
2025-06-10 19:28 ` |WARNING| " dpdklab
2025-06-10 20:25 ` |FAILURE| " dpdklab
2025-06-10 20:29 ` |SUCCESS| " dpdklab
2025-06-10 20:29 ` dpdklab
2025-06-10 20:59 ` dpdklab
2025-06-10 21:02 ` dpdklab
2025-06-10 21:02 ` dpdklab
2025-06-10 21:02 ` dpdklab
2025-06-10 21:02 ` dpdklab
2025-06-10 21:02 ` dpdklab
2025-06-10 22:12 ` |FAILURE| " dpdklab
2025-06-11 2:24 ` |PENDING| " dpdklab
2025-06-11 2:28 ` |WARNING| " dpdklab
2025-06-11 2:29 ` dpdklab
2025-06-11 2:29 ` dpdklab
2025-06-11 2:30 ` dpdklab
2025-06-11 2:30 ` dpdklab
2025-06-11 2:31 ` dpdklab
2025-06-11 2:32 ` dpdklab
2025-06-11 4:10 ` |SUCCESS| " dpdklab
2025-06-11 6:49 ` |FAILURE| " dpdklab
2025-06-11 8:47 ` |SUCCESS| " dpdklab
2025-06-11 8:49 ` |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=202506101429.55AETjCn224916@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=rjarry@redhat.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).