From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw159052-159061 [PATCH v8 10/10] test: re-enable format-truncation warnings
Date: Sat, 29 Nov 2025 06:18:47 +0800 [thread overview]
Message-ID: <202511282218.5ASMIlTA2261235@localhost.localdomain> (raw)
In-Reply-To: <20251128224420.195013-11-stephen@networkplumber.org>
Test-Label: loongarch-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/159061
_Unit Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Fri, 28 Nov 2025 14:42:04 -0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: d4695b3e82a26e6a81b1b96175431469ac2b01d0
159052-159061 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+---------------------+----------------+
| Loongnix-Server 8.3 | PASS |
+---------------------+----------------+
Loongnix-Server 8.3
Kernel: 4.19.190+
Compiler: gcc 8.3
Test result details:
1/110 DPDK:fast-tests / acl_autotest OK 3.27s
2/110 DPDK:fast-tests / alarm_autotest OK 1.56s
3/110 DPDK:fast-tests / argparse_autotest OK 0.56s
4/110 DPDK:fast-tests / atomic_autotest OK 6.94s
5/110 DPDK:fast-tests / bitcount_autotest OK 0.54s
6/110 DPDK:fast-tests / bitmap_autotest OK 0.55s
7/110 DPDK:fast-tests / bitops_autotest OK 2.06s
8/110 DPDK:fast-tests / bitratestats_autotest OK 0.55s
9/110 DPDK:fast-tests / bitset_autotest OK 3.33s
10/110 DPDK:fast-tests / bpf_autotest OK 0.56s
11/110 DPDK:fast-tests / bpf_elf_autotest SKIP 0.55s exit status 77
12/110 DPDK:fast-tests / bpf_convert_autotest OK 0.55s
13/110 DPDK:fast-tests / byteorder_autotest OK 0.55s
14/110 DPDK:fast-tests / cfgfile_autotest OK 0.55s
15/110 DPDK:fast-tests / cksum_autotest OK 0.55s
16/110 DPDK:fast-tests / cmdline_autotest OK 0.55s
17/110 DPDK:fast-tests / common_autotest OK 1.38s
18/110 DPDK:fast-tests / compressdev_autotest SKIP 0.08s exit status 77
19/110 DPDK:fast-tests / cpuflags_autotest OK 0.55s
20/110 DPDK:fast-tests / crc_autotest OK 0.54s
21/110 DPDK:fast-tests / user_delay_us OK 0.54s
22/110 DPDK:fast-tests / debug_autotest OK 17.84s
23/110 DPDK:fast-tests / devargs_autotest OK 0.55s
24/110 DPDK:fast-tests / dispatcher_autotest OK 2.49s
25/110 DPDK:fast-tests / distributor_autotest OK 1.22s
26/110 DPDK:fast-tests / eal_flags_autotest OK 26.52s
27/110 DPDK:fast-tests / eal_fs_autotest OK 0.53s
28/110 DPDK:fast-tests / errno_autotest OK 0.54s
29/110 DPDK:fast-tests / ethdev_link_status OK 0.54s
30/110 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.71s
31/110 DPDK:fast-tests / event_ring_autotest OK 0.55s
32/110 DPDK:fast-tests / eventdev_common_autotest OK 0.54s
33/110 DPDK:fast-tests / eventdev_selftest_sw OK 7.55s
34/110 DPDK:fast-tests / fbarray_autotest OK 0.56s
35/110 DPDK:fast-tests / fib_autotest OK 1.38s
36/110 DPDK:fast-tests / fib6_autotest OK 1.37s
37/110 DPDK:fast-tests / func_reentrancy_autotest OK 2.39s
38/110 DPDK:fast-tests / graph_autotest OK 0.55s
39/110 DPDK:fast-tests / node_list_dump OK 0.44s
40/110 DPDK:fast-tests / graph_feature_arc_autotest OK 0.65s
41/110 DPDK:fast-tests / hash_autotest OK 1.05s
42/110 DPDK:fast-tests / hash_readwrite_func_autotest OK 0.12s
43/110 DPDK:fast-tests / interrupt_autotest OK 1.71s
44/110 DPDK:fast-tests / ipfrag_autotest OK 0.08s
45/110 DPDK:fast-tests / ipsec_autotest SKIP 0.53s exit status 77
46/110 DPDK:fast-tests / kvargs_autotest OK 0.55s
47/110 DPDK:fast-tests / latencystats_autotest OK 0.44s
48/110 DPDK:fast-tests / lcore_var_autotest OK 0.71s
49/110 DPDK:fast-tests / lcores_autotest OK 5.24s
50/110 DPDK:fast-tests / logs_autotest OK 0.44s
51/110 DPDK:fast-tests / lpm_autotest OK 2.57s
52/110 DPDK:fast-tests / lpm6_autotest OK 5.68s
53/110 DPDK:fast-tests / malloc_autotest OK 59.86s
54/110 DPDK:fast-tests / mbuf_autotest OK 4.69s
55/110 DPDK:fast-tests / mcslock_autotest OK 4.71s
56/110 DPDK:fast-tests / member_autotest OK 1.65s
57/110 DPDK:fast-tests / memcpy_autotest OK 6.96s
58/110 DPDK:fast-tests / memory_autotest OK 0.10s
59/110 DPDK:fast-tests / mempool_autotest OK 0.44s
60/110 DPDK:fast-tests / memzone_autotest OK 0.32s
61/110 DPDK:fast-tests / meter_autotest OK 0.54s
62/110 DPDK:fast-tests / metrics_autotest OK 0.44s
63/110 DPDK:fast-tests / multiprocess_autotest OK 0.22s
64/110 DPDK:fast-tests / net_ether_autotest OK 1.11s
65/110 DPDK:fast-tests / net_ipv6_autotest OK 0.44s
66/110 DPDK:fast-tests / pcapng_autotest OK 6.10s
67/110 DPDK:fast-tests / pdcp_autotest SKIP 0.08s exit status 77
68/110 DPDK:fast-tests / pdump_autotest OK 0.52s
69/110 DPDK:fast-tests / per_lcore_autotest OK 0.53s
70/110 DPDK:fast-tests / pflock_autotest OK 1.26s
71/110 DPDK:fast-tests / pie_autotest OK 0.41s
72/110 DPDK:fast-tests / ring_pmd_autotest OK 0.43s
73/110 DPDK:fast-tests / power_autotest OK 0.53s
74/110 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.08s exit status 77
75/110 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.54s exit status 77
76/110 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.08s exit status 77
77/110 DPDK:fast-tests / prefetch_autotest OK 0.43s
78/110 DPDK:fast-tests / ptr_compress_autotest OK 0.44s
79/110 DPDK:fast-tests / rawdev_autotest OK 0.43s
80/110 DPDK:fast-tests / rcu_qsbr_autotest OK 1.04s
81/110 DPDK:fast-tests / reorder_autotest OK 0.49s
82/110 DPDK:fast-tests / rib_autotest OK 9.08s
83/110 DPDK:fast-tests / rib6_autotest OK 9.07s
84/110 DPDK:fast-tests / ring_autotest OK 0.46s
85/110 DPDK:fast-tests / rwlock_test1_autotest OK 1.21s
86/110 DPDK:fast-tests / rwlock_rda_autotest OK 5.44s
87/110 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.44s
88/110 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.42s
89/110 DPDK:fast-tests / sched_autotest OK 0.44s
90/110 DPDK:fast-tests / security_autotest OK 0.08s
91/110 DPDK:fast-tests / seqlock_autotest OK 2.43s
92/110 DPDK:fast-tests / service_autotest OK 3.14s
93/110 DPDK:fast-tests / soring_autotest OK 0.44s
94/110 DPDK:fast-tests / spinlock_autotest OK 0.61s
95/110 DPDK:fast-tests / stack_autotest OK 0.88s
96/110 DPDK:fast-tests / stack_lf_autotest SKIP 0.07s exit status 77
97/110 DPDK:fast-tests / string_autotest OK 0.54s
98/110 DPDK:fast-tests / table_autotest OK 7.89s
99/110 DPDK:fast-tests / tailq_autotest OK 0.54s
100/110 DPDK:fast-tests / telemetry_data_autotest OK 0.44s
101/110 DPDK:fast-tests / telemetry_json_autotest OK 0.54s
102/110 DPDK:fast-tests / thash_autotest OK 0.45s
103/110 DPDK:fast-tests / threads_autotest OK 0.63s
104/110 DPDK:fast-tests / ticketlock_autotest OK 0.70s
105/110 DPDK:fast-tests / timer_autotest OK 3.97s
106/110 DPDK:fast-tests / trace_autotest OK 0.43s
107/110 DPDK:fast-tests / trace_autotest_with_traces OK 0.44s
108/110 DPDK:fast-tests / vdev_autotest OK 0.43s
109/110 DPDK:fast-tests / version_autotest OK 0.44s
110/110 DPDK:fast-tests / telemetry_all OK 19.50s
Ok: 102
Expected Fail: 0
Fail: 0
Unexpected Pass: 0
Skipped: 8
Timeout: 0
next prev parent reply other threads:[~2025-11-28 22:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251128224420.195013-11-stephen@networkplumber.org>
2025-11-28 22:13 ` qemudev
2025-11-28 22:18 ` qemudev [this message]
2025-11-28 22:44 ` |SUCCESS| pw159061 " checkpatch
2025-11-29 1:10 ` |FAILURE| " 0-day Robot
2025-11-29 13:15 ` |PENDING| pw159052-159061 [PATCH] [v8,10/10] test: re-enable format- dpdklab
2025-11-29 13:16 ` |SUCCESS| " dpdklab
2025-11-29 13:19 ` |PENDING| " dpdklab
2025-11-29 13:20 ` |SUCCESS| " dpdklab
2025-11-29 13:24 ` |PENDING| " dpdklab
2025-11-29 13:24 ` |FAILURE| " dpdklab
2025-11-29 13:25 ` |PENDING| " dpdklab
2025-11-29 13:25 ` dpdklab
2025-11-29 13:33 ` |SUCCESS| " dpdklab
2025-11-29 13:36 ` dpdklab
2025-11-29 13:37 ` dpdklab
2025-11-29 13:46 ` dpdklab
2025-11-29 13:50 ` dpdklab
2025-11-29 13:53 ` dpdklab
2025-11-29 13:54 ` dpdklab
2025-11-29 13:56 ` |FAILURE| " dpdklab
2025-11-29 14:00 ` |SUCCESS| " dpdklab
2025-11-29 14:22 ` |FAILURE| " dpdklab
2025-11-29 15:15 ` dpdklab
2025-11-29 16:28 ` |SUCCESS| " 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=202511282218.5ASMIlTA2261235@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=test-report@dpdk.org \
/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).