From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Dengdui Huang <huangdengdui@huawei.com>, zhoumin@loongson.cn
Subject: |FAILURE| pw138202-138203 [PATCH 3/3] app/testpmd: support setting lanes
Date: Tue, 12 Mar 2024 15:36:40 +0800 [thread overview]
Message-ID: <202403120736.42C7aeS42986672@localhost.localdomain> (raw)
In-Reply-To: <20240312075238.3319480-4-huangdengdui@huawei.com>
Test-Label: loongarch-unit-testing
Test-Status: FAILURE
http://dpdk.org/patch/138203
_Unit Testing FAIL_
Submitter: Dengdui Huang <huangdengdui@huawei.com>
Date: Tue, 12 Mar 2024 15:52:36 +0800
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: e3faaed01e14ffdfe8f4190030540ed874184b55
138202-138203 --> 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/112 DPDK:fast-tests / acl_autotest OK 3.38s
2/112 DPDK:fast-tests / argparse_autotest OK 0.67s
3/112 DPDK:fast-tests / atomic_autotest OK 8.63s
4/112 DPDK:fast-tests / bitcount_autotest OK 0.32s
5/112 DPDK:fast-tests / bitmap_autotest OK 0.32s
6/112 DPDK:fast-tests / bitops_autotest OK 0.32s
7/112 DPDK:fast-tests / bitratestats_autotest OK 0.32s
8/112 DPDK:fast-tests / bpf_autotest OK 0.32s
9/112 DPDK:fast-tests / bpf_convert_autotest OK 0.32s
10/112 DPDK:fast-tests / byteorder_autotest OK 0.32s
11/112 DPDK:fast-tests / cksum_autotest OK 0.32s
12/112 DPDK:fast-tests / cmdline_autotest OK 0.32s
13/112 DPDK:fast-tests / common_autotest OK 1.17s
14/112 DPDK:fast-tests / compressdev_autotest SKIP 0.07s exit status 77
15/112 DPDK:fast-tests / cpuflags_autotest OK 0.47s
16/112 DPDK:fast-tests / crc_autotest OK 0.47s
17/112 DPDK:fast-tests / user_delay_us OK 0.47s
18/112 DPDK:fast-tests / debug_autotest OK 15.61s
19/112 DPDK:fast-tests / devargs_autotest OK 0.47s
20/112 DPDK:fast-tests / dispatcher_autotest OK 2.47s
21/112 DPDK:fast-tests / distributor_autotest OK 1.27s
22/112 DPDK:fast-tests / eal_flags_c_opt_autotest OK 1.17s
23/112 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.32s
24/112 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.27s
25/112 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.17s
26/112 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.32s
27/112 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.42s
28/112 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.37s
29/112 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.27s
30/112 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.27s
31/112 DPDK:fast-tests / eal_flags_mem_autotest OK 0.72s
32/112 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 22.37s
33/112 DPDK:fast-tests / eal_flags_misc_autotest OK 1.12s
34/112 DPDK:fast-tests / eal_fs_autotest OK 0.47s
35/112 DPDK:fast-tests / errno_autotest OK 0.47s
36/112 DPDK:fast-tests / ethdev_link_status FAIL 0.47s exit status 255
37/112 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.72s
38/112 DPDK:fast-tests / event_ring_autotest OK 0.47s
39/112 DPDK:fast-tests / eventdev_common_autotest OK 0.47s
40/112 DPDK:fast-tests / eventdev_selftest_sw OK 7.43s
41/112 DPDK:fast-tests / fbarray_autotest OK 0.47s
42/112 DPDK:fast-tests / fib_autotest OK 1.12s
43/112 DPDK:fast-tests / fib6_autotest OK 1.17s
44/112 DPDK:fast-tests / func_reentrancy_autotest OK 2.33s
45/112 DPDK:fast-tests / graph_autotest OK 0.47s
46/112 DPDK:fast-tests / node_list_dump OK 0.67s
47/112 DPDK:fast-tests / hash_autotest OK 1.52s
48/112 DPDK:fast-tests / hash_readwrite_func_autotest OK 6.44s
49/112 DPDK:fast-tests / interrupt_autotest OK 1.83s
50/112 DPDK:fast-tests / ipfrag_autotest OK 0.12s
51/112 DPDK:fast-tests / ipsec_autotest SKIP 0.32s exit status 77
52/112 DPDK:fast-tests / kvargs_autotest OK 0.57s
53/112 DPDK:fast-tests / latencystats_autotest OK 0.47s
54/112 DPDK:fast-tests / lcores_autotest OK 5.13s
55/112 DPDK:fast-tests / logs_autotest OK 0.57s
56/112 DPDK:fast-tests / lpm_autotest OK 2.48s
57/112 DPDK:fast-tests / lpm6_autotest OK 5.70s
58/112 DPDK:fast-tests / malloc_autotest OK 61.23s
59/112 DPDK:fast-tests / mbuf_autotest OK 5.13s
60/112 DPDK:fast-tests / mcslock_autotest OK 4.68s
61/112 DPDK:fast-tests / member_autotest OK 1.67s
62/112 DPDK:fast-tests / memcpy_autotest OK 7.13s
63/112 DPDK:fast-tests / memory_autotest OK 0.12s
64/112 DPDK:fast-tests / mempool_autotest OK 0.47s
65/112 DPDK:fast-tests / memzone_autotest OK 0.17s
66/112 DPDK:fast-tests / meter_autotest OK 0.52s
67/112 DPDK:fast-tests / metrics_autotest OK 0.52s
68/112 DPDK:fast-tests / multiprocess_autotest OK 0.27s
69/112 DPDK:fast-tests / net_ether_autotest OK 1.17s
70/112 DPDK:fast-tests / pcapng_autotest OK 6.93s
71/112 DPDK:fast-tests / pdcp_autotest SKIP 0.12s exit status 77
72/112 DPDK:fast-tests / pdump_autotest OK 0.62s
73/112 DPDK:fast-tests / per_lcore_autotest OK 0.62s
74/112 DPDK:fast-tests / pflock_autotest OK 1.32s
75/112 DPDK:fast-tests / pie_autotest OK 0.52s
76/112 DPDK:fast-tests / ring_pmd_autotest OK 0.52s
77/112 DPDK:fast-tests / power_autotest OK 0.52s
78/112 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.12s exit status 77
79/112 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.52s exit status 77
80/112 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.12s exit status 77
81/112 DPDK:fast-tests / prefetch_autotest OK 0.52s
82/112 DPDK:fast-tests / rawdev_autotest OK 0.52s
83/112 DPDK:fast-tests / rcu_qsbr_autotest OK 1.02s
84/112 DPDK:fast-tests / reorder_autotest OK 0.57s
85/112 DPDK:fast-tests / rib_autotest OK 9.19s
86/112 DPDK:fast-tests / rib6_autotest OK 9.19s
87/112 DPDK:fast-tests / ring_autotest OK 0.52s
88/112 DPDK:fast-tests / rwlock_test1_autotest OK 1.27s
89/112 DPDK:fast-tests / rwlock_rda_autotest OK 5.53s
90/112 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.53s
91/112 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.53s
92/112 DPDK:fast-tests / sched_autotest OK 0.52s
93/112 DPDK:fast-tests / security_autotest OK 0.12s
94/112 DPDK:fast-tests / seqlock_autotest OK 2.52s
95/112 DPDK:fast-tests / service_autotest OK 3.22s
96/112 DPDK:fast-tests / spinlock_autotest OK 0.57s
97/112 DPDK:fast-tests / stack_autotest OK 0.92s
98/112 DPDK:fast-tests / stack_lf_autotest SKIP 0.07s exit status 77
99/112 DPDK:fast-tests / string_autotest OK 0.52s
100/112 DPDK:fast-tests / table_autotest OK 7.74s
101/112 DPDK:fast-tests / tailq_autotest OK 0.52s
102/112 DPDK:fast-tests / telemetry_data_autotest OK 0.52s
103/112 DPDK:fast-tests / telemetry_json_autotest OK 0.52s
104/112 DPDK:fast-tests / thash_autotest OK 0.52s
105/112 DPDK:fast-tests / threads_autotest OK 0.67s
106/112 DPDK:fast-tests / ticketlock_autotest OK 0.67s
107/112 DPDK:fast-tests / timer_autotest OK 4.08s
108/112 DPDK:fast-tests / trace_autotest OK 0.52s
109/112 DPDK:fast-tests / trace_autotest_with_traces OK 0.52s
110/112 DPDK:fast-tests / vdev_autotest OK 0.52s
111/112 DPDK:fast-tests / version_autotest OK 0.52s
112/112 DPDK:fast-tests / telemetry_all OK 1.42s
Ok: 104
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 7
Timeout: 0
Test logs for failed test cases:
================================================================================
DPDK:fast-tests / ethdev_link_status: FAIL
================================================================================
-------------------------------------stdout-------------------------------------
RTE>>ethdev_link_status
+ ------------------------------------------------------- +
+ Test Suite : link status formatting
+ ------------------------------------------------------- +
Default link up #1: Link up at 2.5 Gbps 0lanes FDX Autoneg
TestCase test_link_status_up_default() line 28 failed: Invalid default link status string
+ TestCase [ 0] : test_link_status_up_default failed
+ TestCase [ 1] : test_link_status_down_default succeeded
+ TestCase [ 2] : test_link_speed_all_values succeeded
invalid link up #1: len=37 Link up at Invalid 0lanes FDX Autoneg
TestCase test_link_status_invalid() line 104 failed: Incorrect invalid link status string
+ TestCase [ 3] : test_link_status_invalid failed
+ ------------------------------------------------------- +
+ Test Suite Summary : link status formatting
+ ------------------------------------------------------- +
+ Tests Total : 4
+ Tests Skipped : 0
+ Tests Executed : 4
+ Tests Unsupported: 0
+ Tests Passed : 2
+ 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'
TELEMETRY: No legacy callbacks, legacy socket not created
APP: HPET is not enabled, using TSC as default timer
EAL: lib.eal log level changed from info to debug
next prev parent reply other threads:[~2024-03-12 8:01 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240312075238.3319480-4-huangdengdui@huawei.com>
2024-03-12 7:32 ` |SUCCESS| " qemudev
2024-03-12 7:36 ` qemudev [this message]
2024-03-12 7:53 ` |SUCCESS| pw138203 " checkpatch
2024-03-12 8:42 ` |FAILURE| " 0-day Robot
2024-03-12 9:50 ` |SUCCESS| pw138202-138203 [PATCH] [3/3] app/testpmd: support setting dpdklab
2024-03-12 9:59 ` dpdklab
2024-03-12 10:12 ` dpdklab
2024-03-12 10:12 ` dpdklab
2024-03-12 10:13 ` dpdklab
2024-03-12 10:13 ` dpdklab
2024-03-12 10:14 ` dpdklab
2024-03-12 10:21 ` dpdklab
2024-03-12 10:22 ` dpdklab
2024-03-12 10:22 ` dpdklab
2024-03-12 10:23 ` dpdklab
2024-03-12 10:23 ` |WARNING| " dpdklab
2024-03-12 10:23 ` |SUCCESS| " dpdklab
2024-03-12 10:23 ` |FAILURE| " dpdklab
2024-03-12 10:23 ` |WARNING| " dpdklab
2024-03-12 10:23 ` dpdklab
2024-03-12 10:24 ` |SUCCESS| " dpdklab
2024-03-12 10:24 ` dpdklab
2024-03-12 10:24 ` dpdklab
2024-03-12 10:24 ` dpdklab
2024-03-12 10:25 ` dpdklab
2024-03-12 10:25 ` dpdklab
2024-03-12 10:25 ` dpdklab
2024-03-12 10:25 ` dpdklab
2024-03-12 10:26 ` dpdklab
2024-03-12 10:29 ` |WARNING| " dpdklab
2024-03-12 10:30 ` |SUCCESS| " dpdklab
2024-03-12 10:31 ` |WARNING| " dpdklab
2024-03-12 10:31 ` dpdklab
2024-03-12 10:32 ` |SUCCESS| " dpdklab
2024-03-12 10:32 ` dpdklab
2024-03-12 10:33 ` dpdklab
2024-03-12 10:33 ` |WARNING| " dpdklab
2024-03-12 10:34 ` dpdklab
2024-03-12 10:34 ` |SUCCESS| " dpdklab
2024-03-12 10:34 ` |FAILURE| " dpdklab
2024-03-12 10:35 ` |SUCCESS| " dpdklab
2024-03-12 10:35 ` |WARNING| " dpdklab
2024-03-12 10:35 ` |SUCCESS| " dpdklab
2024-03-12 10:36 ` dpdklab
2024-03-12 10:36 ` |FAILURE| " dpdklab
2024-03-12 10:36 ` |WARNING| " dpdklab
2024-03-12 10:37 ` |FAILURE| " dpdklab
2024-03-12 10:37 ` |SUCCESS| " dpdklab
2024-03-12 10:37 ` dpdklab
2024-03-12 10:37 ` |FAILURE| " dpdklab
2024-03-12 10:37 ` |SUCCESS| " dpdklab
2024-03-12 10:41 ` |FAILURE| " dpdklab
2024-03-12 10:41 ` dpdklab
2024-03-12 10:41 ` dpdklab
2024-03-12 10:43 ` dpdklab
2024-03-12 10:44 ` dpdklab
2024-03-12 10:50 ` dpdklab
2024-03-12 10:53 ` dpdklab
2024-03-12 10:58 ` dpdklab
2024-03-12 10:58 ` dpdklab
2024-03-12 10:58 ` |SUCCESS| " dpdklab
2024-03-12 10:59 ` |FAILURE| " dpdklab
2024-03-12 11:00 ` |SUCCESS| " dpdklab
2024-03-12 11:01 ` |FAILURE| " dpdklab
2024-03-12 11:06 ` dpdklab
2024-03-12 11:07 ` |SUCCESS| " dpdklab
2024-03-12 11:08 ` |FAILURE| " dpdklab
2024-03-12 11:08 ` |SUCCESS| " dpdklab
2024-03-12 11:09 ` |FAILURE| " dpdklab
2024-03-12 11:09 ` |SUCCESS| " dpdklab
2024-03-12 11:11 ` dpdklab
2024-03-12 11:15 ` |FAILURE| " dpdklab
2024-03-12 11:18 ` |SUCCESS| " dpdklab
2024-03-12 12:10 ` dpdklab
2024-03-12 12:24 ` dpdklab
2024-03-12 13:11 ` dpdklab
2024-03-15 20:07 ` dpdklab
2024-03-15 20:36 ` 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=202403120736.42C7aeS42986672@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).