From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw156709 [PATCH] net/mlx5: fix MTU initialization in device spawn
Date: Thu, 18 Sep 2025 13:14:31 +0800 [thread overview]
Message-ID: <202509180514.58I5EVHh1768518@localhost.localdomain> (raw)
In-Reply-To: <20250918054325.777881-1-shperetz@nvidia.com>
Test-Label: loongarch-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/156709
_Unit Testing PASS_
Submitter: Shani Peretz <shperetz@nvidia.com>
Date: Thu, 18 Sep 2025 08:43:25 +0300
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 3d88a77f5c20eb2ff7312f56e4d47b2f79c3a4b9
156709 --> 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/120 DPDK:fast-tests / acl_autotest OK 3.30s
2/120 DPDK:fast-tests / alarm_autotest OK 1.54s
3/120 DPDK:fast-tests / argparse_autotest OK 0.54s
4/120 DPDK:fast-tests / atomic_autotest OK 7.24s
5/120 DPDK:fast-tests / bitcount_autotest OK 0.32s
6/120 DPDK:fast-tests / bitmap_autotest OK 0.53s
7/120 DPDK:fast-tests / bitops_autotest OK 2.03s
8/120 DPDK:fast-tests / bitratestats_autotest OK 0.53s
9/120 DPDK:fast-tests / bitset_autotest OK 3.22s
10/120 DPDK:fast-tests / bpf_autotest OK 0.54s
11/120 DPDK:fast-tests / bpf_convert_autotest OK 0.53s
12/120 DPDK:fast-tests / byteorder_autotest OK 0.53s
13/120 DPDK:fast-tests / cfgfile_autotest OK 0.53s
14/120 DPDK:fast-tests / cksum_autotest OK 0.53s
15/120 DPDK:fast-tests / cmdline_autotest OK 0.55s
16/120 DPDK:fast-tests / common_autotest OK 1.42s
17/120 DPDK:fast-tests / compressdev_autotest SKIP 0.07s exit status 77
18/120 DPDK:fast-tests / cpuflags_autotest OK 0.54s
19/120 DPDK:fast-tests / crc_autotest OK 0.54s
20/120 DPDK:fast-tests / user_delay_us OK 0.54s
21/120 DPDK:fast-tests / debug_autotest OK 19.59s
22/120 DPDK:fast-tests / devargs_autotest OK 0.54s
23/120 DPDK:fast-tests / dispatcher_autotest OK 2.55s
24/120 DPDK:fast-tests / distributor_autotest OK 1.21s
25/120 DPDK:fast-tests / eal_flags_c_opt_autotest OK 0.81s
26/120 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.23s
27/120 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.21s
28/120 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.14s
29/120 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.23s
30/120 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.32s
31/120 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.26s
32/120 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.21s
33/120 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.20s
34/120 DPDK:fast-tests / eal_flags_mem_autotest OK 0.61s
35/120 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 22.23s
36/120 DPDK:fast-tests / eal_flags_misc_autotest OK 1.11s
37/120 DPDK:fast-tests / eal_fs_autotest OK 0.54s
38/120 DPDK:fast-tests / errno_autotest OK 0.54s
39/120 DPDK:fast-tests / ethdev_link_status OK 0.61s
40/120 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.69s
41/120 DPDK:fast-tests / event_ring_autotest OK 0.64s
42/120 DPDK:fast-tests / eventdev_common_autotest OK 0.63s
43/120 DPDK:fast-tests / eventdev_selftest_sw OK 7.55s
44/120 DPDK:fast-tests / fbarray_autotest OK 0.65s
45/120 DPDK:fast-tests / fib_autotest OK 1.47s
46/120 DPDK:fast-tests / fib6_autotest OK 1.28s
47/120 DPDK:fast-tests / func_reentrancy_autotest OK 2.20s
48/120 DPDK:fast-tests / graph_autotest OK 0.43s
49/120 DPDK:fast-tests / node_list_dump OK 0.43s
50/120 DPDK:fast-tests / graph_feature_arc_autotest OK 0.44s
51/120 DPDK:fast-tests / hash_autotest OK 1.06s
52/120 DPDK:fast-tests / hash_readwrite_func_autotest OK 6.41s
53/120 DPDK:fast-tests / interrupt_autotest OK 1.83s
54/120 DPDK:fast-tests / ipfrag_autotest OK 0.07s
55/120 DPDK:fast-tests / ipsec_autotest SKIP 0.43s exit status 77
56/120 DPDK:fast-tests / kvargs_autotest OK 0.43s
57/120 DPDK:fast-tests / latencystats_autotest OK 0.44s
58/120 DPDK:fast-tests / lcore_var_autotest OK 0.57s
59/120 DPDK:fast-tests / lcores_autotest OK 5.34s
60/120 DPDK:fast-tests / logs_autotest OK 0.43s
61/120 DPDK:fast-tests / lpm_autotest OK 2.69s
62/120 DPDK:fast-tests / lpm6_autotest OK 5.56s
63/120 DPDK:fast-tests / malloc_autotest OK 60.96s
64/120 DPDK:fast-tests / mbuf_autotest OK 5.36s
65/120 DPDK:fast-tests / mcslock_autotest OK 4.10s
66/120 DPDK:fast-tests / member_autotest OK 1.62s
67/120 DPDK:fast-tests / memcpy_autotest OK 7.13s
68/120 DPDK:fast-tests / memory_autotest OK 0.10s
69/120 DPDK:fast-tests / mempool_autotest OK 0.44s
70/120 DPDK:fast-tests / memzone_autotest OK 0.14s
71/120 DPDK:fast-tests / meter_autotest OK 0.42s
72/120 DPDK:fast-tests / metrics_autotest OK 0.53s
73/120 DPDK:fast-tests / multiprocess_autotest OK 0.19s
74/120 DPDK:fast-tests / net_ether_autotest OK 1.09s
75/120 DPDK:fast-tests / net_ipv6_autotest OK 0.43s
76/120 DPDK:fast-tests / pcapng_autotest OK 6.04s
77/120 DPDK:fast-tests / pdcp_autotest SKIP 0.07s exit status 77
78/120 DPDK:fast-tests / pdump_autotest OK 0.53s
79/120 DPDK:fast-tests / per_lcore_autotest OK 0.53s
80/120 DPDK:fast-tests / pflock_autotest OK 1.24s
81/120 DPDK:fast-tests / pie_autotest OK 0.43s
82/120 DPDK:fast-tests / ring_pmd_autotest OK 0.43s
83/120 DPDK:fast-tests / power_autotest OK 0.43s
84/120 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.07s exit status 77
85/120 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.42s exit status 77
86/120 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.07s exit status 77
87/120 DPDK:fast-tests / prefetch_autotest OK 0.52s
88/120 DPDK:fast-tests / ptr_compress_autotest OK 0.43s
89/120 DPDK:fast-tests / rawdev_autotest OK 0.43s
90/120 DPDK:fast-tests / rcu_qsbr_autotest OK 0.95s
91/120 DPDK:fast-tests / reorder_autotest OK 0.60s
92/120 DPDK:fast-tests / rib_autotest OK 9.16s
93/120 DPDK:fast-tests / rib6_autotest OK 9.17s
94/120 DPDK:fast-tests / ring_autotest OK 0.60s
95/120 DPDK:fast-tests / rwlock_test1_autotest OK 1.18s
96/120 DPDK:fast-tests / rwlock_rda_autotest OK 5.53s
97/120 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.55s
98/120 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.43s
99/120 DPDK:fast-tests / sched_autotest OK 0.54s
100/120 DPDK:fast-tests / security_autotest OK 0.07s
101/120 DPDK:fast-tests / seqlock_autotest OK 2.43s
102/120 DPDK:fast-tests / service_autotest OK 3.31s
103/120 DPDK:fast-tests / soring_autotest OK 0.44s
104/120 DPDK:fast-tests / spinlock_autotest OK 0.62s
105/120 DPDK:fast-tests / stack_autotest OK 0.86s
106/120 DPDK:fast-tests / stack_lf_autotest SKIP 0.06s exit status 77
107/120 DPDK:fast-tests / string_autotest OK 0.42s
108/120 DPDK:fast-tests / table_autotest OK 7.78s
109/120 DPDK:fast-tests / tailq_autotest OK 0.54s
110/120 DPDK:fast-tests / telemetry_data_autotest OK 0.43s
111/120 DPDK:fast-tests / telemetry_json_autotest OK 0.54s
112/120 DPDK:fast-tests / thash_autotest OK 0.44s
113/120 DPDK:fast-tests / threads_autotest OK 0.74s
114/120 DPDK:fast-tests / ticketlock_autotest OK 0.59s
115/120 DPDK:fast-tests / timer_autotest OK 3.95s
116/120 DPDK:fast-tests / trace_autotest OK 0.42s
117/120 DPDK:fast-tests / trace_autotest_with_traces OK 0.43s
118/120 DPDK:fast-tests / vdev_autotest OK 0.43s
119/120 DPDK:fast-tests / version_autotest OK 0.53s
120/120 DPDK:fast-tests / telemetry_all OK 19.50s
Ok: 113
Expected Fail: 0
Fail: 0
Unexpected Pass: 0
Skipped: 7
Timeout: 0
next prev parent reply other threads:[~2025-09-18 5:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250918054325.777881-1-shperetz@nvidia.com>
2025-09-18 5:09 ` qemudev
2025-09-18 5:14 ` qemudev [this message]
2025-09-18 5:41 ` checkpatch
2025-09-18 6:13 ` |PENDING| pw156709 [PATCH] net/mlx5: fix MTU initialization in devic dpdklab
2025-09-18 6:14 ` dpdklab
2025-09-18 6:14 ` |SUCCESS| " dpdklab
2025-09-18 6:16 ` dpdklab
2025-09-18 6:21 ` |PENDING| " dpdklab
2025-09-18 6:24 ` dpdklab
2025-09-18 6:33 ` |SUCCESS| " dpdklab
2025-09-18 6:37 ` dpdklab
2025-09-18 6:42 ` |PENDING| " dpdklab
2025-09-18 6:43 ` |SUCCESS| " dpdklab
2025-09-18 7:00 ` dpdklab
2025-09-18 7:04 ` |SUCCESS| pw156709 [PATCH] net/mlx5: fix MTU initialization in device spawn 0-day Robot
2025-09-18 7:04 ` 0-day Robot
2025-09-18 7:07 ` |SUCCESS| pw156709 [PATCH] net/mlx5: fix MTU initialization in devic dpdklab
2025-09-18 7:07 ` dpdklab
2025-09-18 7:08 ` dpdklab
2025-09-18 7:17 ` dpdklab
2025-09-18 7:52 ` dpdklab
2025-09-18 8:39 ` dpdklab
2025-09-18 10:13 ` 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=202509180514.58I5EVHh1768518@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).