From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Robin Jarry <rjarry@redhat.com>, zhoumin@loongson.cn
Subject: |FAILURE| pw145917-145918 [PATCH dpdk v3 2/2] ethdev: fix potential race in telemetry endpoints
Date: Tue, 15 Oct 2024 03:29:45 +0800 [thread overview]
Message-ID: <202410141929.49EJTjjS2907701@localhost.localdomain> (raw)
In-Reply-To: <20241014193237.1992382-3-rjarry@redhat.com>
Test-Label: loongarch-unit-testing
Test-Status: FAILURE
http://dpdk.org/patch/145918
_Unit Testing FAIL_
Submitter: Robin Jarry <rjarry@redhat.com>
Date: Mon, 14 Oct 2024 21:32:36 +0200
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 5f7b98189de733080656989d63b0e7ffd249830a
145917-145918 --> 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/115 DPDK:fast-tests / acl_autotest OK 3.42s
2/115 DPDK:fast-tests / alarm_autotest OK 1.65s
3/115 DPDK:fast-tests / argparse_autotest OK 0.64s
4/115 DPDK:fast-tests / atomic_autotest OK 7.13s
5/115 DPDK:fast-tests / bitcount_autotest OK 0.32s
6/115 DPDK:fast-tests / bitmap_autotest OK 0.32s
7/115 DPDK:fast-tests / bitops_autotest OK 1.82s
8/115 DPDK:fast-tests / bitratestats_autotest OK 0.32s
9/115 DPDK:fast-tests / bitset_autotest OK 2.98s
10/115 DPDK:fast-tests / bpf_autotest OK 0.32s
11/115 DPDK:fast-tests / bpf_convert_autotest OK 0.32s
12/115 DPDK:fast-tests / byteorder_autotest OK 0.52s
13/115 DPDK:fast-tests / cksum_autotest OK 0.52s
14/115 DPDK:fast-tests / cmdline_autotest OK 0.52s
15/115 DPDK:fast-tests / common_autotest OK 1.35s
16/115 DPDK:fast-tests / compressdev_autotest SKIP 0.07s exit status 77
17/115 DPDK:fast-tests / cpuflags_autotest OK 0.40s
18/115 DPDK:fast-tests / crc_autotest OK 0.52s
19/115 DPDK:fast-tests / user_delay_us OK 0.51s
20/115 DPDK:fast-tests / debug_autotest OK 24.42s
21/115 DPDK:fast-tests / devargs_autotest OK 0.40s
22/115 DPDK:fast-tests / dispatcher_autotest OK 2.61s
23/115 DPDK:fast-tests / distributor_autotest OK 1.23s
24/115 DPDK:fast-tests / eal_flags_c_opt_autotest OK 1.14s
25/115 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.29s
26/115 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.26s
27/115 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.16s
28/115 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.29s
29/115 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.41s
30/115 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.33s
31/115 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.24s
32/115 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.24s
33/115 DPDK:fast-tests / eal_flags_mem_autotest OK 0.71s
34/115 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 22.37s
35/115 DPDK:fast-tests / eal_flags_misc_autotest OK 1.10s
36/115 DPDK:fast-tests / eal_fs_autotest OK 0.31s
37/115 DPDK:fast-tests / errno_autotest OK 0.31s
38/115 DPDK:fast-tests / ethdev_link_status OK 0.42s
39/115 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.71s
40/115 DPDK:fast-tests / event_ring_autotest OK 0.32s
41/115 DPDK:fast-tests / eventdev_common_autotest OK 0.31s
42/115 DPDK:fast-tests / eventdev_selftest_sw OK 7.22s
43/115 DPDK:fast-tests / fbarray_autotest OK 0.32s
44/115 DPDK:fast-tests / fib_autotest FAIL 0.96s exit status 255
45/115 DPDK:fast-tests / fib6_autotest OK 0.98s
46/115 DPDK:fast-tests / func_reentrancy_autotest OK 2.09s
47/115 DPDK:fast-tests / graph_autotest OK 0.32s
48/115 DPDK:fast-tests / node_list_dump OK 0.31s
49/115 DPDK:fast-tests / hash_autotest OK 1.11s
50/115 DPDK:fast-tests / hash_readwrite_func_autotest OK 6.42s
51/115 DPDK:fast-tests / interrupt_autotest OK 1.62s
52/115 DPDK:fast-tests / ipfrag_autotest OK 0.08s
53/115 DPDK:fast-tests / ipsec_autotest SKIP 0.32s exit status 77
54/115 DPDK:fast-tests / kvargs_autotest OK 0.32s
55/115 DPDK:fast-tests / latencystats_autotest OK 0.32s
56/115 DPDK:fast-tests / lcores_autotest OK 5.12s
57/115 DPDK:fast-tests / logs_autotest OK 0.31s
58/115 DPDK:fast-tests / lpm_autotest OK 2.39s
59/115 DPDK:fast-tests / lpm6_autotest OK 5.51s
60/115 DPDK:fast-tests / malloc_autotest OK 62.89s
61/115 DPDK:fast-tests / mbuf_autotest OK 4.40s
62/115 DPDK:fast-tests / mcslock_autotest OK 2.73s
63/115 DPDK:fast-tests / member_autotest OK 1.48s
64/115 DPDK:fast-tests / memcpy_autotest OK 6.91s
65/115 DPDK:fast-tests / memory_autotest OK 0.09s
66/115 DPDK:fast-tests / mempool_autotest OK 0.44s
67/115 DPDK:fast-tests / memzone_autotest OK 0.14s
68/115 DPDK:fast-tests / meter_autotest OK 0.31s
69/115 DPDK:fast-tests / metrics_autotest OK 0.31s
70/115 DPDK:fast-tests / multiprocess_autotest OK 0.22s
71/115 DPDK:fast-tests / net_ether_autotest OK 0.98s
72/115 DPDK:fast-tests / pcapng_autotest OK 6.88s
73/115 DPDK:fast-tests / pdcp_autotest SKIP 0.07s exit status 77
74/115 DPDK:fast-tests / pdump_autotest OK 0.43s
75/115 DPDK:fast-tests / per_lcore_autotest OK 0.41s
76/115 DPDK:fast-tests / pflock_autotest OK 1.12s
77/115 DPDK:fast-tests / pie_autotest OK 0.32s
78/115 DPDK:fast-tests / ring_pmd_autotest OK 0.31s
79/115 DPDK:fast-tests / power_autotest OK 0.31s
80/115 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.07s exit status 77
81/115 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.31s exit status 77
82/115 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.07s exit status 77
83/115 DPDK:fast-tests / prefetch_autotest OK 0.31s
84/115 DPDK:fast-tests / ptr_compress_autotest OK 0.31s
85/115 DPDK:fast-tests / rawdev_autotest OK 0.31s
86/115 DPDK:fast-tests / rcu_qsbr_autotest OK 0.83s
87/115 DPDK:fast-tests / reorder_autotest OK 0.37s
88/115 DPDK:fast-tests / rib_autotest OK 8.98s
89/115 DPDK:fast-tests / rib6_autotest OK 8.98s
90/115 DPDK:fast-tests / ring_autotest OK 0.35s
91/115 DPDK:fast-tests / rwlock_test1_autotest OK 1.06s
92/115 DPDK:fast-tests / rwlock_rda_autotest OK 5.32s
93/115 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.32s
94/115 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.32s
95/115 DPDK:fast-tests / sched_autotest OK 0.32s
96/115 DPDK:fast-tests / security_autotest OK 0.07s
97/115 DPDK:fast-tests / seqlock_autotest OK 2.31s
98/115 DPDK:fast-tests / service_autotest OK 3.04s
99/115 DPDK:fast-tests / spinlock_autotest OK 0.39s
100/115 DPDK:fast-tests / stack_autotest OK 0.87s
101/115 DPDK:fast-tests / stack_lf_autotest SKIP 0.06s exit status 77
102/115 DPDK:fast-tests / string_autotest OK 0.31s
103/115 DPDK:fast-tests / table_autotest OK 7.69s
104/115 DPDK:fast-tests / tailq_autotest OK 0.31s
105/115 DPDK:fast-tests / telemetry_data_autotest OK 0.32s
106/115 DPDK:fast-tests / telemetry_json_autotest OK 0.31s
107/115 DPDK:fast-tests / thash_autotest OK 0.32s
108/115 DPDK:fast-tests / threads_autotest OK 0.50s
109/115 DPDK:fast-tests / ticketlock_autotest OK 0.47s
110/115 DPDK:fast-tests / timer_autotest OK 3.91s
111/115 DPDK:fast-tests / trace_autotest OK 0.31s
112/115 DPDK:fast-tests / trace_autotest_with_traces OK 0.32s
113/115 DPDK:fast-tests / vdev_autotest OK 0.31s
114/115 DPDK:fast-tests / version_autotest OK 0.31s
115/115 DPDK:fast-tests / telemetry_all OK 1.24s
Ok: 107
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 7
Timeout: 0
Test logs for failed test cases:
================================================================================
DPDK:fast-tests / fib_autotest: FAIL
================================================================================
-------------------------------------stdout-------------------------------------
RTE>>fib_autotest
+ ------------------------------------------------------- +
+ Test Suite : fib 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 failed
+ TestCase [ 6] : test_fib_rcu_sync_rw failed
+ ------------------------------------------------------- +
+ Test Suite Summary : fib autotest
+ ------------------------------------------------------- +
+ Tests Total : 7
+ Tests Skipped : 0
+ Tests Executed : 7
+ Tests Unsupported: 0
+ Tests Passed : 5
+ Tests Failed : 2
+ ------------------------------------------------------- +
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 RIB 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 with err -22
FIB: FIB dataplane struct test_create_invalid memory allocation failed with err -22
EAL: Test assert test_invalid_rcu line 406 failed: Failed to create FIB
EAL: Test assert test_fib_rcu_sync_rw line 527 failed: Failed to create FIB
next prev parent reply other threads:[~2024-10-14 19:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241014193237.1992382-3-rjarry@redhat.com>
2024-10-14 19:25 ` |SUCCESS| " qemudev
2024-10-14 19:29 ` qemudev [this message]
2024-10-14 19:33 ` |SUCCESS| pw145918 " checkpatch
2024-10-14 20:22 ` |FAILURE| " 0-day Robot
2024-10-15 1:10 ` |SUCCESS| pw145917-145918 [PATCH] [v3,2/2] ethdev: fix potential rac dpdklab
2024-10-15 3:16 ` dpdklab
2024-10-15 4:34 ` dpdklab
2024-10-15 7:04 ` dpdklab
2024-10-15 12:27 ` dpdklab
2024-10-15 12:58 ` |WARNING| " dpdklab
2024-10-17 3:18 ` |SUCCESS| " dpdklab
2024-10-22 12:06 ` dpdklab
2024-10-23 4:03 ` |WARNING| " dpdklab
2024-10-23 4:26 ` 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=202410141929.49EJTjjS2907701@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).