From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>, zhoumin@loongson.cn
Subject: |FAILURE| pw132222 [RFC] rte_ether_unformat: accept more inputs
Date: Sat, 30 Sep 2023 00:21:55 +0800 [thread overview]
Message-ID: <202309291621.38TGLtcW973824@localhost.localdomain> (raw)
In-Reply-To: <20230929163611.62691-1-stephen@networkplumber.org>
Test-Label: loongarch-unit-testing
Test-Status: FAILURE
http://dpdk.org/patch/132222
_Unit Testing FAIL_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Fri, 29 Sep 2023 09:36:11 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 6e999364a6afb9189029154b1ac55b4ad5fb9b3f
132222 --> 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/107 DPDK:fast-tests / acl_autotest OK 3.33s
2/107 DPDK:fast-tests / atomic_autotest OK 7.23s
3/107 DPDK:fast-tests / bitcount_autotest OK 0.47s
4/107 DPDK:fast-tests / bitmap_autotest OK 0.47s
5/107 DPDK:fast-tests / bitops_autotest OK 0.47s
6/107 DPDK:fast-tests / bitratestats_autotest OK 0.47s
7/107 DPDK:fast-tests / bpf_autotest OK 0.47s
8/107 DPDK:fast-tests / bpf_convert_autotest OK 0.47s
9/107 DPDK:fast-tests / byteorder_autotest OK 0.47s
10/107 DPDK:fast-tests / cksum_autotest OK 0.47s
11/107 DPDK:fast-tests / cmdline_autotest FAIL 0.47s exit status 255
12/107 DPDK:fast-tests / common_autotest OK 1.32s
13/107 DPDK:fast-tests / compressdev_autotest SKIP 0.12s exit status 77
14/107 DPDK:fast-tests / cpuflags_autotest OK 0.47s
15/107 DPDK:fast-tests / crc_autotest OK 0.47s
16/107 DPDK:fast-tests / user_delay_us OK 0.47s
17/107 DPDK:fast-tests / debug_autotest OK 16.77s
18/107 DPDK:fast-tests / devargs_autotest OK 0.52s
19/107 DPDK:fast-tests / distributor_autotest OK 1.27s
20/107 DPDK:fast-tests / eal_flags_c_opt_autotest OK 1.22s
21/107 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.32s
22/107 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.27s
23/107 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.17s
24/107 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.32s
25/107 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.42s
26/107 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.37s
27/107 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.27s
28/107 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.28s
29/107 DPDK:fast-tests / eal_flags_mem_autotest OK 0.72s
30/107 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 22.37s
31/107 DPDK:fast-tests / eal_flags_misc_autotest OK 1.18s
32/107 DPDK:fast-tests / eal_fs_autotest OK 0.52s
33/107 DPDK:fast-tests / errno_autotest OK 0.52s
34/107 DPDK:fast-tests / ethdev_link_status OK 0.52s
35/107 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.72s
36/107 DPDK:fast-tests / event_ring_autotest OK 0.52s
37/107 DPDK:fast-tests / eventdev_common_autotest OK 0.52s
38/107 DPDK:fast-tests / fbarray_autotest OK 0.52s
39/107 DPDK:fast-tests / fib_autotest OK 1.17s
40/107 DPDK:fast-tests / fib6_autotest OK 1.22s
41/107 DPDK:fast-tests / func_reentrancy_autotest OK 2.23s
42/107 DPDK:fast-tests / graph_autotest OK 0.52s
43/107 DPDK:fast-tests / node_list_dump OK 0.52s
44/107 DPDK:fast-tests / hash_autotest OK 1.42s
45/107 DPDK:fast-tests / hash_readwrite_func_autotest OK 6.49s
46/107 DPDK:fast-tests / interrupt_autotest OK 1.82s
47/107 DPDK:fast-tests / ipfrag_autotest OK 0.12s
48/107 DPDK:fast-tests / ipsec_autotest SKIP 0.52s exit status 77
49/107 DPDK:fast-tests / kvargs_autotest OK 0.52s
50/107 DPDK:fast-tests / latencystats_autotest OK 0.52s
51/107 DPDK:fast-tests / lcores_autotest OK 5.53s
52/107 DPDK:fast-tests / logs_autotest OK 0.52s
53/107 DPDK:fast-tests / lpm_autotest OK 2.53s
54/107 DPDK:fast-tests / lpm6_autotest OK 5.75s
55/107 DPDK:fast-tests / malloc_autotest OK 63.41s
56/107 DPDK:fast-tests / mbuf_autotest OK 4.62s
57/107 DPDK:fast-tests / mcslock_autotest OK 4.43s
58/107 DPDK:fast-tests / member_autotest OK 1.67s
59/107 DPDK:fast-tests / memcpy_autotest OK 7.13s
60/107 DPDK:fast-tests / memory_autotest OK 0.12s
61/107 DPDK:fast-tests / mempool_autotest OK 0.47s
62/107 DPDK:fast-tests / memzone_autotest OK 0.17s
63/107 DPDK:fast-tests / meter_autotest OK 0.52s
64/107 DPDK:fast-tests / metrics_autotest OK 0.52s
65/107 DPDK:fast-tests / multiprocess_autotest OK 0.27s
66/107 DPDK:fast-tests / pdcp_autotest SKIP 0.07s exit status 77
67/107 DPDK:fast-tests / pdump_autotest OK 0.62s
68/107 DPDK:fast-tests / per_lcore_autotest OK 0.62s
69/107 DPDK:fast-tests / pflock_autotest OK 1.32s
70/107 DPDK:fast-tests / pie_autotest OK 0.52s
71/107 DPDK:fast-tests / ring_pmd_autotest OK 0.52s
72/107 DPDK:fast-tests / power_autotest OK 0.52s
73/107 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.12s exit status 77
74/107 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.52s exit status 77
75/107 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.12s exit status 77
76/107 DPDK:fast-tests / prefetch_autotest OK 0.52s
77/107 DPDK:fast-tests / rawdev_autotest OK 0.52s
78/107 DPDK:fast-tests / rcu_qsbr_autotest OK 1.02s
79/107 DPDK:fast-tests / reorder_autotest OK 0.57s
80/107 DPDK:fast-tests / rib_autotest OK 9.19s
81/107 DPDK:fast-tests / rib6_autotest OK 9.19s
82/107 DPDK:fast-tests / ring_autotest OK 0.52s
83/107 DPDK:fast-tests / rwlock_test1_autotest OK 1.27s
84/107 DPDK:fast-tests / rwlock_rda_autotest OK 5.53s
85/107 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.53s
86/107 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.53s
87/107 DPDK:fast-tests / sched_autotest OK 0.52s
88/107 DPDK:fast-tests / security_autotest OK 0.07s
89/107 DPDK:fast-tests / seqlock_autotest OK 2.48s
90/107 DPDK:fast-tests / service_autotest OK 3.33s
91/107 DPDK:fast-tests / spinlock_autotest OK 0.63s
92/107 DPDK:fast-tests / stack_autotest OK 0.92s
93/107 DPDK:fast-tests / stack_lf_autotest SKIP 0.07s exit status 77
94/107 DPDK:fast-tests / string_autotest OK 0.52s
95/107 DPDK:fast-tests / table_autotest OK 8.09s
96/107 DPDK:fast-tests / tailq_autotest OK 0.48s
97/107 DPDK:fast-tests / telemetry_data_autotest OK 0.52s
98/107 DPDK:fast-tests / telemetry_json_autotest OK 0.52s
99/107 DPDK:fast-tests / thash_autotest OK 0.52s
100/107 DPDK:fast-tests / threads_autotest OK 0.69s
101/107 DPDK:fast-tests / ticketlock_autotest OK 0.72s
102/107 DPDK:fast-tests / timer_autotest OK 4.08s
103/107 DPDK:fast-tests / trace_autotest OK 0.52s
104/107 DPDK:fast-tests / trace_autotest_with_traces OK 0.52s
105/107 DPDK:fast-tests / vdev_autotest OK 0.52s
106/107 DPDK:fast-tests / version_autotest OK 0.52s
107/107 DPDK:fast-tests / telemetry_all OK 1.47s
Ok: 99
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 7
Timeout: 0
Test logs for failed test cases:
================================================================================
DPDK:fast-tests / cmdline_autotest: FAIL
================================================================================
-------------------------------------stdout-------------------------------------
RTE>>cmdline_autotest
Testind parsing ethernet addresses...
Error: parsing 01.23.45.67.89.AB succeeded!
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
next prev parent reply other threads:[~2023-09-29 16:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230929163611.62691-1-stephen@networkplumber.org>
2023-09-29 16:17 ` |SUCCESS| " qemudev
2023-09-29 16:21 ` qemudev [this message]
2023-09-29 16:37 ` |WARNING| " checkpatch
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=202309291621.38TGLtcW973824@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=stephen@networkplumber.org \
--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).