From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw148303 [PATCH] power: fix a typo in the PM QoS guide
Date: Mon, 11 Nov 2024 20:38:28 +0800 [thread overview]
Message-ID: <202411111238.4ABCcSR6918926@localhost.localdomain> (raw)
In-Reply-To: <20241111125249.9824-1-lihuisong@huawei.com>
Test-Label: loongarch-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/148303
_Unit Testing PASS_
Submitter: Huisong Li <lihuisong@huawei.com>
Date: Mon, 11 Nov 2024 20:52:49 +0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 89398ecec0486f91e1d9302ae2fb454f3b2dd012
148303 --> 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/117 DPDK:fast-tests / acl_autotest OK 3.34s
2/117 DPDK:fast-tests / alarm_autotest OK 1.52s
3/117 DPDK:fast-tests / argparse_autotest OK 0.53s
4/117 DPDK:fast-tests / atomic_autotest OK 7.24s
5/117 DPDK:fast-tests / bitcount_autotest OK 0.43s
6/117 DPDK:fast-tests / bitmap_autotest OK 0.43s
7/117 DPDK:fast-tests / bitops_autotest OK 1.93s
8/117 DPDK:fast-tests / bitratestats_autotest OK 0.44s
9/117 DPDK:fast-tests / bitset_autotest OK 3.03s
10/117 DPDK:fast-tests / bpf_autotest OK 0.44s
11/117 DPDK:fast-tests / bpf_convert_autotest OK 0.44s
12/117 DPDK:fast-tests / byteorder_autotest OK 0.43s
13/117 DPDK:fast-tests / cksum_autotest OK 0.44s
14/117 DPDK:fast-tests / cmdline_autotest OK 0.44s
15/117 DPDK:fast-tests / common_autotest OK 1.27s
16/117 DPDK:fast-tests / compressdev_autotest SKIP 0.07s exit status 77
17/117 DPDK:fast-tests / cpuflags_autotest OK 0.43s
18/117 DPDK:fast-tests / crc_autotest OK 0.44s
19/117 DPDK:fast-tests / user_delay_us OK 0.43s
20/117 DPDK:fast-tests / debug_autotest OK 15.76s
21/117 DPDK:fast-tests / devargs_autotest OK 0.43s
22/117 DPDK:fast-tests / dispatcher_autotest OK 2.60s
23/117 DPDK:fast-tests / distributor_autotest OK 1.22s
24/117 DPDK:fast-tests / eal_flags_c_opt_autotest OK 1.14s
25/117 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.29s
26/117 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.26s
27/117 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.16s
28/117 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.29s
29/117 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.41s
30/117 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.33s
31/117 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.24s
32/117 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.25s
33/117 DPDK:fast-tests / eal_flags_mem_autotest OK 0.71s
34/117 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 22.36s
35/117 DPDK:fast-tests / eal_flags_misc_autotest OK 1.34s
36/117 DPDK:fast-tests / eal_fs_autotest OK 0.43s
37/117 DPDK:fast-tests / errno_autotest OK 0.43s
38/117 DPDK:fast-tests / ethdev_link_status OK 0.43s
39/117 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.69s
40/117 DPDK:fast-tests / event_ring_autotest OK 0.44s
41/117 DPDK:fast-tests / eventdev_common_autotest OK 0.44s
42/117 DPDK:fast-tests / eventdev_selftest_sw OK 7.41s
43/117 DPDK:fast-tests / fbarray_autotest OK 0.44s
44/117 DPDK:fast-tests / fib_autotest OK 1.33s
45/117 DPDK:fast-tests / fib6_autotest OK 1.11s
46/117 DPDK:fast-tests / func_reentrancy_autotest OK 2.27s
47/117 DPDK:fast-tests / graph_autotest OK 0.44s
48/117 DPDK:fast-tests / node_list_dump OK 0.43s
49/117 DPDK:fast-tests / hash_autotest OK 1.07s
50/117 DPDK:fast-tests / hash_readwrite_func_autotest OK 6.42s
51/117 DPDK:fast-tests / interrupt_autotest OK 1.74s
52/117 DPDK:fast-tests / ipfrag_autotest OK 0.08s
53/117 DPDK:fast-tests / ipsec_autotest SKIP 0.44s exit status 77
54/117 DPDK:fast-tests / kvargs_autotest OK 0.44s
55/117 DPDK:fast-tests / latencystats_autotest OK 0.44s
56/117 DPDK:fast-tests / lcore_var_autotest OK 0.58s
57/117 DPDK:fast-tests / lcores_autotest OK 5.24s
58/117 DPDK:fast-tests / logs_autotest OK 0.43s
59/117 DPDK:fast-tests / lpm_autotest OK 2.49s
60/117 DPDK:fast-tests / lpm6_autotest OK 5.62s
61/117 DPDK:fast-tests / malloc_autotest OK 61.17s
62/117 DPDK:fast-tests / mbuf_autotest OK 4.99s
63/117 DPDK:fast-tests / mcslock_autotest OK 3.30s
64/117 DPDK:fast-tests / member_autotest OK 1.63s
65/117 DPDK:fast-tests / memcpy_autotest OK 6.80s
66/117 DPDK:fast-tests / memory_autotest OK 0.09s
67/117 DPDK:fast-tests / mempool_autotest OK 0.44s
68/117 DPDK:fast-tests / memzone_autotest OK 0.15s
69/117 DPDK:fast-tests / meter_autotest OK 0.43s
70/117 DPDK:fast-tests / metrics_autotest OK 0.44s
71/117 DPDK:fast-tests / multiprocess_autotest OK 0.23s
72/117 DPDK:fast-tests / net_ether_autotest OK 1.10s
73/117 DPDK:fast-tests / net_ipv6_autotest OK 0.44s
74/117 DPDK:fast-tests / pcapng_autotest OK 7.56s
75/117 DPDK:fast-tests / pdcp_autotest SKIP 0.07s exit status 77
76/117 DPDK:fast-tests / pdump_autotest OK 0.56s
77/117 DPDK:fast-tests / per_lcore_autotest OK 0.54s
78/117 DPDK:fast-tests / pflock_autotest OK 1.26s
79/117 DPDK:fast-tests / pie_autotest OK 0.44s
80/117 DPDK:fast-tests / ring_pmd_autotest OK 0.44s
81/117 DPDK:fast-tests / power_autotest OK 0.43s
82/117 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.07s exit status 77
83/117 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.43s exit status 77
84/117 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.07s exit status 77
85/117 DPDK:fast-tests / prefetch_autotest OK 0.43s
86/117 DPDK:fast-tests / ptr_compress_autotest OK 0.43s
87/117 DPDK:fast-tests / rawdev_autotest OK 0.43s
88/117 DPDK:fast-tests / rcu_qsbr_autotest OK 0.95s
89/117 DPDK:fast-tests / reorder_autotest OK 0.49s
90/117 DPDK:fast-tests / rib_autotest OK 9.08s
91/117 DPDK:fast-tests / rib6_autotest OK 9.02s
92/117 DPDK:fast-tests / ring_autotest OK 0.46s
93/117 DPDK:fast-tests / rwlock_test1_autotest OK 1.21s
94/117 DPDK:fast-tests / rwlock_rda_autotest OK 5.44s
95/117 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.43s
96/117 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.54s
97/117 DPDK:fast-tests / sched_autotest OK 0.44s
98/117 DPDK:fast-tests / security_autotest OK 0.07s
99/117 DPDK:fast-tests / seqlock_autotest OK 2.42s
100/117 DPDK:fast-tests / service_autotest OK 3.14s
101/117 DPDK:fast-tests / spinlock_autotest OK 0.52s
102/117 DPDK:fast-tests / stack_autotest OK 0.87s
103/117 DPDK:fast-tests / stack_lf_autotest SKIP 0.06s exit status 77
104/117 DPDK:fast-tests / string_autotest OK 0.43s
105/117 DPDK:fast-tests / table_autotest OK 7.63s
106/117 DPDK:fast-tests / tailq_autotest OK 0.43s
107/117 DPDK:fast-tests / telemetry_data_autotest OK 0.44s
108/117 DPDK:fast-tests / telemetry_json_autotest OK 0.43s
109/117 DPDK:fast-tests / thash_autotest OK 0.45s
110/117 DPDK:fast-tests / threads_autotest OK 0.62s
111/117 DPDK:fast-tests / ticketlock_autotest OK 0.61s
112/117 DPDK:fast-tests / timer_autotest OK 3.95s
113/117 DPDK:fast-tests / trace_autotest OK 0.43s
114/117 DPDK:fast-tests / trace_autotest_with_traces OK 0.44s
115/117 DPDK:fast-tests / vdev_autotest OK 0.43s
116/117 DPDK:fast-tests / version_autotest OK 0.43s
117/117 DPDK:fast-tests / telemetry_all OK 1.35s
Ok: 110
Expected Fail: 0
Fail: 0
Unexpected Pass: 0
Skipped: 7
Timeout: 0
next prev parent reply other threads:[~2024-11-11 13:12 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241111125249.9824-1-lihuisong@huawei.com>
2024-11-11 12:33 ` qemudev
2024-11-11 12:38 ` qemudev [this message]
2024-11-11 13:04 ` checkpatch
2024-11-11 14:06 ` 0-day Robot
2024-11-11 16:40 ` dpdklab
2024-11-11 16:54 ` dpdklab
2024-11-11 16:58 ` dpdklab
2024-11-11 17:02 ` dpdklab
2024-11-11 17:06 ` dpdklab
2024-11-11 17:09 ` dpdklab
2024-11-11 17:11 ` dpdklab
2024-11-11 17:15 ` |PENDING| " dpdklab
2024-11-11 17:21 ` dpdklab
2024-11-11 17:28 ` |SUCCESS| " dpdklab
2024-11-11 17:29 ` dpdklab
2024-11-11 17:31 ` dpdklab
2024-11-11 17:35 ` dpdklab
2024-11-11 17:40 ` dpdklab
2024-11-11 17:46 ` dpdklab
2024-11-11 17:47 ` dpdklab
2024-11-11 18:07 ` |WARNING| " dpdklab
2024-11-11 18:08 ` |SUCCESS| " dpdklab
2024-11-11 18:20 ` dpdklab
2024-11-11 18:23 ` dpdklab
2024-11-11 18:29 ` |PENDING| " dpdklab
2024-11-11 18:35 ` dpdklab
2024-11-11 18:47 ` |SUCCESS| " dpdklab
2024-11-11 18:50 ` |PENDING| " dpdklab
2024-11-11 19:08 ` |SUCCESS| " dpdklab
2024-11-11 19:13 ` dpdklab
2024-11-11 19:15 ` dpdklab
2024-11-11 19:18 ` |WARNING| " dpdklab
2024-11-11 19:22 ` dpdklab
2024-11-11 19:39 ` dpdklab
2024-11-11 19:40 ` |SUCCESS| " dpdklab
2024-11-11 19:56 ` |WARNING| " dpdklab
2024-11-11 20:05 ` |SUCCESS| " dpdklab
2024-11-11 20:14 ` dpdklab
2024-11-11 20:22 ` dpdklab
2024-11-11 20:25 ` dpdklab
2024-11-11 20:39 ` dpdklab
2024-11-11 20:46 ` dpdklab
2024-11-11 20:53 ` |WARNING| " dpdklab
2024-11-11 20:55 ` dpdklab
2024-11-11 21:00 ` |SUCCESS| " dpdklab
2024-11-11 21:00 ` |WARNING| " dpdklab
2024-11-11 21:02 ` dpdklab
2024-11-11 23:31 ` |SUCCESS| " dpdklab
2024-11-11 23:59 ` 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=202411111238.4ABCcSR6918926@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).