From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw131164 [PATCH v2] net/ice: fix tm configuration cannot be cleared
Date: Tue, 5 Sep 2023 15:47:32 +0800 [thread overview]
Message-ID: <202309050747.3857lWDc223114@localhost.localdomain> (raw)
In-Reply-To: <20230905073444.708799-1-kaiwenx.deng@intel.com>
Test-Label: loongarch-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/131164
_Unit Testing PASS_
Submitter: Kaiwen Deng <kaiwenx.deng@intel.com>
Date: Tue, 5 Sep 2023 15:34:44 +0800
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 161bb655ea029d173d4f5144c5b36530cb598718
131164 --> 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/91 DPDK:fast-tests / acl_autotest OK 3.18s
2/91 DPDK:fast-tests / atomic_autotest OK 7.23s
3/91 DPDK:fast-tests / bitmap_autotest OK 0.47s
4/91 DPDK:fast-tests / bitops_autotest OK 0.47s
5/91 DPDK:fast-tests / bpf_autotest OK 0.47s
6/91 DPDK:fast-tests / bpf_convert_autotest OK 0.47s
7/91 DPDK:fast-tests / byteorder_autotest OK 0.47s
8/91 DPDK:fast-tests / cksum_autotest OK 0.47s
9/91 DPDK:fast-tests / cmdline_autotest OK 0.47s
10/91 DPDK:fast-tests / common_autotest OK 1.32s
11/91 DPDK:fast-tests / cpuflags_autotest OK 0.47s
12/91 DPDK:fast-tests / crc_autotest OK 0.47s
13/91 DPDK:fast-tests / user_delay_us OK 0.47s
14/91 DPDK:fast-tests / debug_autotest OK 20.07s
15/91 DPDK:fast-tests / devargs_autotest OK 0.47s
16/91 DPDK:fast-tests / distributor_autotest OK 1.27s
17/91 DPDK:fast-tests / eal_flags_c_opt_autotest OK 1.22s
18/91 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.32s
19/91 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.32s
20/91 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.17s
21/91 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.32s
22/91 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.47s
23/91 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.37s
24/91 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.27s
25/91 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.27s
26/91 DPDK:fast-tests / eal_flags_mem_autotest OK 0.77s
27/91 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 22.41s
28/91 DPDK:fast-tests / eal_flags_misc_autotest OK 1.22s
29/91 DPDK:fast-tests / eal_fs_autotest OK 0.47s
30/91 DPDK:fast-tests / errno_autotest OK 0.47s
31/91 DPDK:fast-tests / ethdev_link_status OK 0.47s
32/91 DPDK:fast-tests / event_ring_autotest OK 0.47s
33/91 DPDK:fast-tests / eventdev_common_autotest OK 0.47s
34/91 DPDK:fast-tests / fbarray_autotest OK 0.47s
35/91 DPDK:fast-tests / fib_autotest OK 1.17s
36/91 DPDK:fast-tests / fib6_autotest OK 1.17s
37/91 DPDK:fast-tests / func_reentrancy_autotest OK 2.28s
38/91 DPDK:fast-tests / hash_autotest OK 1.42s
39/91 DPDK:fast-tests / hash_readwrite_func_autotest OK 6.49s
40/91 DPDK:fast-tests / interrupt_autotest OK 1.72s
41/91 DPDK:fast-tests / ipfrag_autotest OK 0.12s
42/91 DPDK:fast-tests / ipsec_autotest SKIP 0.47s exit status 77
43/91 DPDK:fast-tests / kvargs_autotest OK 0.47s
44/91 DPDK:fast-tests / lcores_autotest OK 5.48s
45/91 DPDK:fast-tests / logs_autotest OK 0.57s
46/91 DPDK:fast-tests / lpm_autotest OK 2.63s
47/91 DPDK:fast-tests / lpm6_autotest OK 5.89s
48/91 DPDK:fast-tests / malloc_autotest OK 63.66s
49/91 DPDK:fast-tests / mbuf_autotest OK 5.43s
50/91 DPDK:fast-tests / mcslock_autotest OK 4.42s
51/91 DPDK:fast-tests / member_autotest OK 1.67s
52/91 DPDK:fast-tests / memcpy_autotest OK 7.33s
53/91 DPDK:fast-tests / memory_autotest OK 0.12s
54/91 DPDK:fast-tests / mempool_autotest OK 0.47s
55/91 DPDK:fast-tests / memzone_autotest OK 0.17s
56/91 DPDK:fast-tests / meter_autotest OK 0.47s
57/91 DPDK:fast-tests / multiprocess_autotest OK 0.27s
58/91 DPDK:fast-tests / per_lcore_autotest OK 0.57s
59/91 DPDK:fast-tests / pflock_autotest OK 1.27s
60/91 DPDK:fast-tests / pie_autotest OK 0.47s
61/91 DPDK:fast-tests / power_autotest OK 0.47s
62/91 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.12s exit status 77
63/91 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.47s exit status 77
64/91 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.12s exit status 77
65/91 DPDK:fast-tests / prefetch_autotest OK 0.47s
66/91 DPDK:fast-tests / rcu_qsbr_autotest OK 0.97s
67/91 DPDK:fast-tests / reorder_autotest OK 0.52s
68/91 DPDK:fast-tests / rib_autotest OK 9.14s
69/91 DPDK:fast-tests / rib6_autotest OK 9.14s
70/91 DPDK:fast-tests / ring_autotest OK 0.47s
71/91 DPDK:fast-tests / rwlock_test1_autotest OK 1.22s
72/91 DPDK:fast-tests / rwlock_rda_autotest OK 5.48s
73/91 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.48s
74/91 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.48s
75/91 DPDK:fast-tests / sched_autotest OK 0.47s
76/91 DPDK:fast-tests / security_autotest OK 0.12s
77/91 DPDK:fast-tests / seqlock_autotest OK 2.47s
78/91 DPDK:fast-tests / service_autotest OK 3.17s
79/91 DPDK:fast-tests / spinlock_autotest OK 0.52s
80/91 DPDK:fast-tests / stack_autotest OK 0.92s
81/91 DPDK:fast-tests / stack_lf_autotest SKIP 0.07s exit status 77
82/91 DPDK:fast-tests / string_autotest OK 0.47s
83/91 DPDK:fast-tests / tailq_autotest OK 0.47s
84/91 DPDK:fast-tests / thash_autotest OK 0.47s
85/91 DPDK:fast-tests / threads_autotest OK 0.62s
86/91 DPDK:fast-tests / ticketlock_autotest OK 0.62s
87/91 DPDK:fast-tests / timer_autotest OK 4.02s
88/91 DPDK:fast-tests / trace_autotest OK 0.47s
89/91 DPDK:fast-tests / trace_autotest_with_traces OK 0.47s
90/91 DPDK:fast-tests / version_autotest OK 0.47s
91/91 DPDK:fast-tests / telemetry_all OK 1.37s
Ok: 86
Expected Fail: 0
Fail: 0
Unexpected Pass: 0
Skipped: 5
Timeout: 0
next prev parent reply other threads:[~2023-09-05 8:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230905073444.708799-1-kaiwenx.deng@intel.com>
2023-09-05 7:43 ` qemudev
2023-09-05 7:47 ` qemudev [this message]
2023-09-05 7:57 ` checkpatch
2023-09-05 8:59 ` 0-day Robot
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=202309050747.3857lWDc223114@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).