From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw158861-158866 [PATCH v3 6/6] test: re-enable format-truncation warnings
Date: Tue, 18 Nov 2025 01:24:29 +0800 [thread overview]
Message-ID: <202511171724.5AHHOTk52382775@localhost.localdomain> (raw)
In-Reply-To: <20251117175332.14014-7-stephen@networkplumber.org>
Test-Label: loongarch-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/158866
_Unit Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Mon, 17 Nov 2025 09:52:08 -0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: be0112878b4fc3a1b918370ed2fe615c52039d77
158861-158866 --> 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/109 DPDK:fast-tests / acl_autotest OK 3.24s
2/109 DPDK:fast-tests / alarm_autotest OK 1.51s
3/109 DPDK:fast-tests / argparse_autotest OK 0.50s
4/109 DPDK:fast-tests / atomic_autotest OK 6.94s
5/109 DPDK:fast-tests / bitcount_autotest OK 0.45s
6/109 DPDK:fast-tests / bitmap_autotest OK 0.44s
7/109 DPDK:fast-tests / bitops_autotest OK 1.94s
8/109 DPDK:fast-tests / bitratestats_autotest OK 0.44s
9/109 DPDK:fast-tests / bitset_autotest OK 3.19s
10/109 DPDK:fast-tests / bpf_autotest OK 0.44s
11/109 DPDK:fast-tests / bpf_convert_autotest OK 0.44s
12/109 DPDK:fast-tests / byteorder_autotest OK 0.44s
13/109 DPDK:fast-tests / cfgfile_autotest OK 0.44s
14/109 DPDK:fast-tests / cksum_autotest OK 0.44s
15/109 DPDK:fast-tests / cmdline_autotest OK 0.44s
16/109 DPDK:fast-tests / common_autotest OK 1.32s
17/109 DPDK:fast-tests / compressdev_autotest SKIP 0.08s exit status 77
18/109 DPDK:fast-tests / cpuflags_autotest OK 0.44s
19/109 DPDK:fast-tests / crc_autotest OK 0.44s
20/109 DPDK:fast-tests / user_delay_us OK 0.44s
21/109 DPDK:fast-tests / debug_autotest OK 19.31s
22/109 DPDK:fast-tests / devargs_autotest OK 0.44s
23/109 DPDK:fast-tests / dispatcher_autotest OK 2.52s
24/109 DPDK:fast-tests / distributor_autotest OK 1.21s
25/109 DPDK:fast-tests / eal_flags_autotest OK 26.64s
26/109 DPDK:fast-tests / eal_fs_autotest OK 0.44s
27/109 DPDK:fast-tests / errno_autotest OK 0.44s
28/109 DPDK:fast-tests / ethdev_link_status OK 0.44s
29/109 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.70s
30/109 DPDK:fast-tests / event_ring_autotest OK 0.44s
31/109 DPDK:fast-tests / eventdev_common_autotest OK 0.44s
32/109 DPDK:fast-tests / eventdev_selftest_sw OK 7.41s
33/109 DPDK:fast-tests / fbarray_autotest OK 0.44s
34/109 DPDK:fast-tests / fib_autotest OK 1.27s
35/109 DPDK:fast-tests / fib6_autotest OK 1.26s
36/109 DPDK:fast-tests / func_reentrancy_autotest OK 2.30s
37/109 DPDK:fast-tests / graph_autotest OK 0.44s
38/109 DPDK:fast-tests / node_list_dump OK 0.44s
39/109 DPDK:fast-tests / graph_feature_arc_autotest OK 0.44s
40/109 DPDK:fast-tests / hash_autotest OK 1.06s
41/109 DPDK:fast-tests / hash_readwrite_func_autotest OK 0.12s
42/109 DPDK:fast-tests / interrupt_autotest OK 1.74s
43/109 DPDK:fast-tests / ipfrag_autotest OK 0.08s
44/109 DPDK:fast-tests / ipsec_autotest SKIP 0.44s exit status 77
45/109 DPDK:fast-tests / kvargs_autotest OK 0.44s
46/109 DPDK:fast-tests / latencystats_autotest OK 0.45s
47/109 DPDK:fast-tests / lcore_var_autotest OK 0.59s
48/109 DPDK:fast-tests / lcores_autotest OK 5.25s
49/109 DPDK:fast-tests / logs_autotest OK 0.44s
50/109 DPDK:fast-tests / lpm_autotest OK 2.48s
51/109 DPDK:fast-tests / lpm6_autotest OK 5.58s
52/109 DPDK:fast-tests / malloc_autotest OK 61.05s
53/109 DPDK:fast-tests / mbuf_autotest OK 4.99s
54/109 DPDK:fast-tests / mcslock_autotest OK 4.13s
55/109 DPDK:fast-tests / member_autotest OK 1.63s
56/109 DPDK:fast-tests / memcpy_autotest OK 6.88s
57/109 DPDK:fast-tests / memory_autotest OK 0.10s
58/109 DPDK:fast-tests / mempool_autotest OK 0.45s
59/109 DPDK:fast-tests / memzone_autotest OK 0.32s
60/109 DPDK:fast-tests / meter_autotest OK 0.44s
61/109 DPDK:fast-tests / metrics_autotest OK 0.44s
62/109 DPDK:fast-tests / multiprocess_autotest OK 0.23s
63/109 DPDK:fast-tests / net_ether_autotest OK 1.10s
64/109 DPDK:fast-tests / net_ipv6_autotest OK 0.44s
65/109 DPDK:fast-tests / pcapng_autotest OK 7.72s
66/109 DPDK:fast-tests / pdcp_autotest SKIP 0.08s exit status 77
67/109 DPDK:fast-tests / pdump_autotest OK 0.54s
68/109 DPDK:fast-tests / per_lcore_autotest OK 0.54s
69/109 DPDK:fast-tests / pflock_autotest OK 1.27s
70/109 DPDK:fast-tests / pie_autotest OK 0.44s
71/109 DPDK:fast-tests / ring_pmd_autotest OK 0.44s
72/109 DPDK:fast-tests / power_autotest OK 0.44s
73/109 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.08s exit status 77
74/109 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.44s exit status 77
75/109 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.08s exit status 77
76/109 DPDK:fast-tests / prefetch_autotest OK 0.44s
77/109 DPDK:fast-tests / ptr_compress_autotest OK 0.44s
78/109 DPDK:fast-tests / rawdev_autotest OK 0.43s
79/109 DPDK:fast-tests / rcu_qsbr_autotest OK 0.96s
80/109 DPDK:fast-tests / reorder_autotest OK 0.50s
81/109 DPDK:fast-tests / rib_autotest OK 9.09s
82/109 DPDK:fast-tests / rib6_autotest OK 9.09s
83/109 DPDK:fast-tests / ring_autotest OK 0.47s
84/109 DPDK:fast-tests / rwlock_test1_autotest OK 1.21s
85/109 DPDK:fast-tests / rwlock_rda_autotest OK 5.44s
86/109 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.44s
87/109 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.55s
88/109 DPDK:fast-tests / sched_autotest OK 0.55s
89/109 DPDK:fast-tests / security_autotest OK 0.08s
90/109 DPDK:fast-tests / seqlock_autotest OK 2.63s
91/109 DPDK:fast-tests / service_autotest OK 3.33s
92/109 DPDK:fast-tests / soring_autotest OK 0.51s
93/109 DPDK:fast-tests / spinlock_autotest OK 0.48s
94/109 DPDK:fast-tests / stack_autotest OK 0.87s
95/109 DPDK:fast-tests / stack_lf_autotest SKIP 0.07s exit status 77
96/109 DPDK:fast-tests / string_autotest OK 0.63s
97/109 DPDK:fast-tests / table_autotest OK 7.71s
98/109 DPDK:fast-tests / tailq_autotest OK 0.61s
99/109 DPDK:fast-tests / telemetry_data_autotest OK 0.62s
100/109 DPDK:fast-tests / telemetry_json_autotest OK 0.61s
101/109 DPDK:fast-tests / thash_autotest OK 0.62s
102/109 DPDK:fast-tests / threads_autotest OK 0.79s
103/109 DPDK:fast-tests / ticketlock_autotest OK 0.77s
104/109 DPDK:fast-tests / timer_autotest OK 3.90s
105/109 DPDK:fast-tests / trace_autotest OK 0.62s
106/109 DPDK:fast-tests / trace_autotest_with_traces OK 0.62s
107/109 DPDK:fast-tests / vdev_autotest OK 0.61s
108/109 DPDK:fast-tests / version_autotest OK 0.61s
109/109 DPDK:fast-tests / telemetry_all OK 19.55s
Ok: 102
Expected Fail: 0
Fail: 0
Unexpected Pass: 0
Skipped: 7
Timeout: 0
next prev parent reply other threads:[~2025-11-17 18:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251117175332.14014-7-stephen@networkplumber.org>
2025-11-17 17:19 ` qemudev
2025-11-17 17:24 ` qemudev [this message]
2025-11-17 17:53 ` |SUCCESS| pw158866 " checkpatch
2025-11-17 18:54 ` |FAILURE| " 0-day Robot
2025-11-18 11:13 ` |FAILURE| pw158861-158866 [PATCH] [v3,6/6] test: re-enable format-tr dpdklab
2025-11-18 11:14 ` |PENDING| " dpdklab
2025-11-18 11:14 ` |SUCCESS| " dpdklab
2025-11-18 11:16 ` |FAILURE| " dpdklab
2025-11-18 11:20 ` |SUCCESS| " dpdklab
2025-11-18 11:21 ` |FAILURE| " dpdklab
2025-11-18 11:23 ` dpdklab
2025-11-18 11:31 ` |SUCCESS| " dpdklab
2025-11-18 11:31 ` |PENDING| " dpdklab
2025-11-18 11:33 ` |WARNING| " dpdklab
2025-11-18 11:33 ` |FAILURE| " dpdklab
2025-11-18 11:33 ` dpdklab
2025-11-18 11:34 ` |SUCCESS| " dpdklab
2025-11-18 11:37 ` dpdklab
2025-11-18 11:37 ` dpdklab
2025-11-18 11:37 ` dpdklab
2025-11-18 11:45 ` |WARNING| " dpdklab
2025-11-18 11:55 ` |SUCCESS| " dpdklab
2025-11-18 12:00 ` |WARNING| " dpdklab
2025-11-18 12:04 ` |FAILURE| " dpdklab
2025-11-18 12:08 ` 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=202511171724.5AHHOTk52382775@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).