From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw146828 [PATCH v3] net/mlx5: fix potential memory leak in meter
Date: Wed, 23 Oct 2024 14:07:35 +0800 [thread overview]
Message-ID: <202410230607.49N67ZlO072556@localhost.localdomain> (raw)
In-Reply-To: <20241023062216.967742-1-shunh@nvidia.com>
Test-Label: loongarch-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/146828
_Unit Testing PASS_
Submitter: Shun Hao <shunh@nvidia.com>
Date: Wed, 23 Oct 2024 09:22:15 +0300
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: c4f029602e46450a0c51953c4607e53488244071
146828 --> 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/116 DPDK:fast-tests / acl_autotest OK 3.18s
2/116 DPDK:fast-tests / alarm_autotest OK 1.43s
3/116 DPDK:fast-tests / argparse_autotest OK 0.42s
4/116 DPDK:fast-tests / atomic_autotest OK 7.27s
5/116 DPDK:fast-tests / bitcount_autotest OK 0.44s
6/116 DPDK:fast-tests / bitmap_autotest OK 0.44s
7/116 DPDK:fast-tests / bitops_autotest OK 1.94s
8/116 DPDK:fast-tests / bitratestats_autotest OK 0.44s
9/116 DPDK:fast-tests / bitset_autotest OK 3.10s
10/116 DPDK:fast-tests / bpf_autotest OK 0.44s
11/116 DPDK:fast-tests / bpf_convert_autotest OK 0.44s
12/116 DPDK:fast-tests / byteorder_autotest OK 0.44s
13/116 DPDK:fast-tests / cksum_autotest OK 0.44s
14/116 DPDK:fast-tests / cmdline_autotest OK 0.44s
15/116 DPDK:fast-tests / common_autotest OK 1.28s
16/116 DPDK:fast-tests / compressdev_autotest SKIP 0.08s exit status 77
17/116 DPDK:fast-tests / cpuflags_autotest OK 0.43s
18/116 DPDK:fast-tests / crc_autotest OK 0.44s
19/116 DPDK:fast-tests / user_delay_us OK 0.44s
20/116 DPDK:fast-tests / debug_autotest OK 14.74s
21/116 DPDK:fast-tests / devargs_autotest OK 0.44s
22/116 DPDK:fast-tests / dispatcher_autotest OK 2.53s
23/116 DPDK:fast-tests / distributor_autotest OK 1.23s
24/116 DPDK:fast-tests / eal_flags_c_opt_autotest OK 1.24s
25/116 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.32s
26/116 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.28s
27/116 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.17s
28/116 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.31s
29/116 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.44s
30/116 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.36s
31/116 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.26s
32/116 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.27s
33/116 DPDK:fast-tests / eal_flags_mem_autotest OK 0.76s
34/116 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 22.45s
35/116 DPDK:fast-tests / eal_flags_misc_autotest OK 1.20s
36/116 DPDK:fast-tests / eal_fs_autotest OK 0.44s
37/116 DPDK:fast-tests / errno_autotest OK 0.44s
38/116 DPDK:fast-tests / ethdev_link_status OK 0.44s
39/116 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.72s
40/116 DPDK:fast-tests / event_ring_autotest OK 0.44s
41/116 DPDK:fast-tests / eventdev_common_autotest OK 0.44s
42/116 DPDK:fast-tests / eventdev_selftest_sw OK 7.33s
43/116 DPDK:fast-tests / fbarray_autotest OK 0.44s
44/116 DPDK:fast-tests / fib_autotest OK 1.36s
45/116 DPDK:fast-tests / fib6_autotest OK 1.13s
46/116 DPDK:fast-tests / func_reentrancy_autotest OK 2.27s
47/116 DPDK:fast-tests / graph_autotest OK 0.44s
48/116 DPDK:fast-tests / node_list_dump OK 0.44s
49/116 DPDK:fast-tests / hash_autotest OK 1.25s
50/116 DPDK:fast-tests / hash_readwrite_func_autotest OK 6.43s
51/116 DPDK:fast-tests / interrupt_autotest OK 1.74s
52/116 DPDK:fast-tests / ipfrag_autotest OK 0.08s
53/116 DPDK:fast-tests / ipsec_autotest SKIP 0.44s exit status 77
54/116 DPDK:fast-tests / kvargs_autotest OK 0.44s
55/116 DPDK:fast-tests / latencystats_autotest OK 0.45s
56/116 DPDK:fast-tests / lcores_autotest OK 5.25s
57/116 DPDK:fast-tests / logs_autotest OK 0.44s
58/116 DPDK:fast-tests / lpm_autotest OK 2.46s
59/116 DPDK:fast-tests / lpm6_autotest OK 5.71s
60/116 DPDK:fast-tests / malloc_autotest OK 63.14s
61/116 DPDK:fast-tests / mbuf_autotest OK 4.71s
62/116 DPDK:fast-tests / mcslock_autotest OK 4.89s
63/116 DPDK:fast-tests / member_autotest OK 1.67s
64/116 DPDK:fast-tests / memcpy_autotest OK 7.03s
65/116 DPDK:fast-tests / memory_autotest OK 0.10s
66/116 DPDK:fast-tests / mempool_autotest OK 0.45s
67/116 DPDK:fast-tests / memzone_autotest OK 0.15s
68/116 DPDK:fast-tests / meter_autotest OK 0.43s
69/116 DPDK:fast-tests / metrics_autotest OK 0.44s
70/116 DPDK:fast-tests / multiprocess_autotest OK 0.25s
71/116 DPDK:fast-tests / net_ether_autotest OK 1.10s
72/116 DPDK:fast-tests / net_ipv6_autotest OK 0.44s
73/116 DPDK:fast-tests / pcapng_autotest OK 6.44s
74/116 DPDK:fast-tests / pdcp_autotest SKIP 0.08s exit status 77
75/116 DPDK:fast-tests / pdump_autotest OK 0.58s
76/116 DPDK:fast-tests / per_lcore_autotest OK 0.54s
77/116 DPDK:fast-tests / pflock_autotest OK 1.27s
78/116 DPDK:fast-tests / pie_autotest OK 0.44s
79/116 DPDK:fast-tests / ring_pmd_autotest OK 0.44s
80/116 DPDK:fast-tests / power_autotest OK 0.44s
81/116 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.08s exit status 77
82/116 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.44s exit status 77
83/116 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.08s exit status 77
84/116 DPDK:fast-tests / prefetch_autotest OK 0.44s
85/116 DPDK:fast-tests / ptr_compress_autotest OK 0.44s
86/116 DPDK:fast-tests / rawdev_autotest OK 0.44s
87/116 DPDK:fast-tests / rcu_qsbr_autotest OK 0.96s
88/116 DPDK:fast-tests / reorder_autotest OK 0.50s
89/116 DPDK:fast-tests / rib_autotest OK 9.12s
90/116 DPDK:fast-tests / rib6_autotest OK 9.10s
91/116 DPDK:fast-tests / ring_autotest OK 0.47s
92/116 DPDK:fast-tests / rwlock_test1_autotest OK 1.22s
93/116 DPDK:fast-tests / rwlock_rda_autotest OK 5.43s
94/116 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.44s
95/116 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.44s
96/116 DPDK:fast-tests / sched_autotest OK 0.44s
97/116 DPDK:fast-tests / security_autotest OK 0.08s
98/116 DPDK:fast-tests / seqlock_autotest OK 2.42s
99/116 DPDK:fast-tests / service_autotest OK 3.16s
100/116 DPDK:fast-tests / spinlock_autotest OK 0.52s
101/116 DPDK:fast-tests / stack_autotest OK 0.88s
102/116 DPDK:fast-tests / stack_lf_autotest SKIP 0.07s exit status 77
103/116 DPDK:fast-tests / string_autotest OK 0.44s
104/116 DPDK:fast-tests / table_autotest OK 7.64s
105/116 DPDK:fast-tests / tailq_autotest OK 0.43s
106/116 DPDK:fast-tests / telemetry_data_autotest OK 0.44s
107/116 DPDK:fast-tests / telemetry_json_autotest OK 0.44s
108/116 DPDK:fast-tests / thash_autotest OK 0.45s
109/116 DPDK:fast-tests / threads_autotest OK 0.61s
110/116 DPDK:fast-tests / ticketlock_autotest OK 0.61s
111/116 DPDK:fast-tests / timer_autotest OK 3.99s
112/116 DPDK:fast-tests / trace_autotest OK 0.44s
113/116 DPDK:fast-tests / trace_autotest_with_traces OK 0.44s
114/116 DPDK:fast-tests / vdev_autotest OK 0.44s
115/116 DPDK:fast-tests / version_autotest OK 0.44s
116/116 DPDK:fast-tests / telemetry_all OK 1.36s
Ok: 109
Expected Fail: 0
Fail: 0
Unexpected Pass: 0
Skipped: 7
Timeout: 0
next prev parent reply other threads:[~2024-10-23 6:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241023062216.967742-1-shunh@nvidia.com>
2024-10-23 6:03 ` qemudev
2024-10-23 6:07 ` qemudev [this message]
2024-10-23 6:23 ` |WARNING| " checkpatch
2024-10-23 7:26 ` |SUCCESS| " 0-day Robot
2024-10-23 12:22 ` |SUCCESS| pw146828 [PATCH] [v3] net/mlx5: fix potential memory leak dpdklab
2024-10-23 17:50 ` dpdklab
2024-10-23 18:02 ` dpdklab
2024-10-23 19:19 ` dpdklab
2024-10-23 21:13 ` dpdklab
2024-10-24 7:07 ` dpdklab
2024-10-24 7:43 ` dpdklab
2024-10-25 1:34 ` |PENDING| " dpdklab
2024-10-25 5:44 ` |SUCCESS| " dpdklab
2024-10-25 6:06 ` dpdklab
2024-10-26 1:40 ` |PENDING| " dpdklab
2024-10-26 1:45 ` |SUCCESS| " dpdklab
2024-10-26 16:49 ` dpdklab
2024-10-27 15:11 ` dpdklab
2024-10-27 21:09 ` dpdklab
2024-10-28 5:49 ` dpdklab
2024-10-28 6:01 ` dpdklab
2024-11-01 22:24 ` dpdklab
2024-11-03 0:43 ` 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=202410230607.49N67ZlO072556@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).