From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw145758 [PATCH v3] bus/pci: don't open uio device in secondary process
Date: Fri, 11 Oct 2024 18:53:43 +0800 [thread overview]
Message-ID: <202410111053.49BArhaN3981866@localhost.localdomain> (raw)
In-Reply-To: <20241011111533.20746-1-konrad.sztyber@intel.com>
Test-Label: loongarch-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/145758
_Unit Testing PASS_
Submitter: Konrad Sztyber <konrad.sztyber@intel.com>
Date: Fri, 11 Oct 2024 13:15:05 +0200
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 93f8d73ac18de2df963698d31d8dd819392deade
145758 --> 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/114 DPDK:fast-tests / acl_autotest OK 3.33s
2/114 DPDK:fast-tests / alarm_autotest OK 1.57s
3/114 DPDK:fast-tests / argparse_autotest OK 0.57s
4/114 DPDK:fast-tests / atomic_autotest OK 7.38s
5/114 DPDK:fast-tests / bitcount_autotest OK 0.42s
6/114 DPDK:fast-tests / bitmap_autotest OK 0.42s
7/114 DPDK:fast-tests / bitops_autotest OK 1.92s
8/114 DPDK:fast-tests / bitratestats_autotest OK 0.42s
9/114 DPDK:fast-tests / bpf_autotest OK 0.42s
10/114 DPDK:fast-tests / bpf_convert_autotest OK 0.42s
11/114 DPDK:fast-tests / byteorder_autotest OK 0.42s
12/114 DPDK:fast-tests / cksum_autotest OK 0.42s
13/114 DPDK:fast-tests / cmdline_autotest OK 0.42s
14/114 DPDK:fast-tests / common_autotest OK 1.32s
15/114 DPDK:fast-tests / compressdev_autotest SKIP 0.12s exit status 77
16/114 DPDK:fast-tests / cpuflags_autotest OK 0.42s
17/114 DPDK:fast-tests / crc_autotest OK 0.42s
18/114 DPDK:fast-tests / user_delay_us OK 0.42s
19/114 DPDK:fast-tests / debug_autotest OK 19.31s
20/114 DPDK:fast-tests / devargs_autotest OK 0.42s
21/114 DPDK:fast-tests / dispatcher_autotest OK 2.57s
22/114 DPDK:fast-tests / distributor_autotest OK 1.22s
23/114 DPDK:fast-tests / eal_flags_c_opt_autotest OK 1.12s
24/114 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.32s
25/114 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.27s
26/114 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.17s
27/114 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.32s
28/114 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.42s
29/114 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.37s
30/114 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.27s
31/114 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.27s
32/114 DPDK:fast-tests / eal_flags_mem_autotest OK 0.72s
33/114 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 22.36s
34/114 DPDK:fast-tests / eal_flags_misc_autotest OK 1.12s
35/114 DPDK:fast-tests / eal_fs_autotest OK 0.42s
36/114 DPDK:fast-tests / errno_autotest OK 0.42s
37/114 DPDK:fast-tests / ethdev_link_status OK 0.42s
38/114 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.72s
39/114 DPDK:fast-tests / event_ring_autotest OK 0.42s
40/114 DPDK:fast-tests / eventdev_common_autotest OK 0.42s
41/114 DPDK:fast-tests / eventdev_selftest_sw OK 7.43s
42/114 DPDK:fast-tests / fbarray_autotest OK 0.42s
43/114 DPDK:fast-tests / fib_autotest OK 1.07s
44/114 DPDK:fast-tests / fib6_autotest OK 1.12s
45/114 DPDK:fast-tests / func_reentrancy_autotest OK 2.28s
46/114 DPDK:fast-tests / graph_autotest OK 0.42s
47/114 DPDK:fast-tests / node_list_dump OK 0.42s
48/114 DPDK:fast-tests / hash_autotest OK 1.27s
49/114 DPDK:fast-tests / hash_readwrite_func_autotest OK 6.48s
50/114 DPDK:fast-tests / interrupt_autotest OK 1.72s
51/114 DPDK:fast-tests / ipfrag_autotest OK 0.12s
52/114 DPDK:fast-tests / ipsec_autotest SKIP 0.42s exit status 77
53/114 DPDK:fast-tests / kvargs_autotest OK 0.42s
54/114 DPDK:fast-tests / latencystats_autotest OK 0.42s
55/114 DPDK:fast-tests / lcores_autotest OK 5.23s
56/114 DPDK:fast-tests / logs_autotest OK 0.42s
57/114 DPDK:fast-tests / lpm_autotest OK 2.48s
58/114 DPDK:fast-tests / lpm6_autotest OK 5.59s
59/114 DPDK:fast-tests / malloc_autotest OK 62.16s
60/114 DPDK:fast-tests / mbuf_autotest OK 5.22s
61/114 DPDK:fast-tests / mcslock_autotest OK 4.17s
62/114 DPDK:fast-tests / member_autotest OK 1.62s
63/114 DPDK:fast-tests / memcpy_autotest OK 7.03s
64/114 DPDK:fast-tests / memory_autotest OK 0.12s
65/114 DPDK:fast-tests / mempool_autotest OK 0.47s
66/114 DPDK:fast-tests / memzone_autotest OK 0.17s
67/114 DPDK:fast-tests / meter_autotest OK 0.42s
68/114 DPDK:fast-tests / metrics_autotest OK 0.42s
69/114 DPDK:fast-tests / multiprocess_autotest OK 0.27s
70/114 DPDK:fast-tests / net_ether_autotest OK 1.07s
71/114 DPDK:fast-tests / pcapng_autotest OK 6.38s
72/114 DPDK:fast-tests / pdcp_autotest SKIP 0.12s exit status 77
73/114 DPDK:fast-tests / pdump_autotest OK 0.52s
74/114 DPDK:fast-tests / per_lcore_autotest OK 0.52s
75/114 DPDK:fast-tests / pflock_autotest OK 1.27s
76/114 DPDK:fast-tests / pie_autotest OK 0.42s
77/114 DPDK:fast-tests / ring_pmd_autotest OK 0.42s
78/114 DPDK:fast-tests / power_autotest OK 0.42s
79/114 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.12s exit status 77
80/114 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.42s exit status 77
81/114 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.12s exit status 77
82/114 DPDK:fast-tests / prefetch_autotest OK 0.42s
83/114 DPDK:fast-tests / ptr_compress_autotest OK 0.42s
84/114 DPDK:fast-tests / rawdev_autotest OK 0.42s
85/114 DPDK:fast-tests / rcu_qsbr_autotest OK 0.92s
86/114 DPDK:fast-tests / reorder_autotest OK 0.47s
87/114 DPDK:fast-tests / rib_autotest OK 9.09s
88/114 DPDK:fast-tests / rib6_autotest OK 9.09s
89/114 DPDK:fast-tests / ring_autotest OK 0.47s
90/114 DPDK:fast-tests / rwlock_test1_autotest OK 1.17s
91/114 DPDK:fast-tests / rwlock_rda_autotest OK 5.43s
92/114 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.43s
93/114 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.43s
94/114 DPDK:fast-tests / sched_autotest OK 0.42s
95/114 DPDK:fast-tests / security_autotest OK 0.12s
96/114 DPDK:fast-tests / seqlock_autotest OK 2.42s
97/114 DPDK:fast-tests / service_autotest OK 3.17s
98/114 DPDK:fast-tests / spinlock_autotest OK 0.52s
99/114 DPDK:fast-tests / stack_autotest OK 0.87s
100/114 DPDK:fast-tests / stack_lf_autotest SKIP 0.07s exit status 77
101/114 DPDK:fast-tests / string_autotest OK 0.42s
102/114 DPDK:fast-tests / table_autotest OK 7.69s
103/114 DPDK:fast-tests / tailq_autotest OK 0.42s
104/114 DPDK:fast-tests / telemetry_data_autotest OK 0.42s
105/114 DPDK:fast-tests / telemetry_json_autotest OK 0.42s
106/114 DPDK:fast-tests / thash_autotest OK 0.42s
107/114 DPDK:fast-tests / threads_autotest OK 0.62s
108/114 DPDK:fast-tests / ticketlock_autotest OK 0.62s
109/114 DPDK:fast-tests / timer_autotest OK 3.92s
110/114 DPDK:fast-tests / trace_autotest OK 0.42s
111/114 DPDK:fast-tests / trace_autotest_with_traces OK 0.42s
112/114 DPDK:fast-tests / vdev_autotest OK 0.42s
113/114 DPDK:fast-tests / version_autotest OK 0.42s
114/114 DPDK:fast-tests / telemetry_all OK 1.37s
Ok: 107
Expected Fail: 0
Fail: 0
Unexpected Pass: 0
Skipped: 7
Timeout: 0
next prev parent reply other threads:[~2024-10-11 11:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241011111533.20746-1-konrad.sztyber@intel.com>
2024-10-11 10:49 ` qemudev
2024-10-11 10:53 ` qemudev [this message]
2024-10-11 11:17 ` |WARNING| " checkpatch
2024-10-11 12:03 ` |SUCCESS| " 0-day Robot
2024-10-11 19:37 ` |PENDING| pw145758 [PATCH] [v3] bus/pci: don't open uio device in se dpdklab
2024-10-11 19:46 ` |SUCCESS| " dpdklab
2024-10-11 20:32 ` |PENDING| " dpdklab
2024-10-11 23:57 ` dpdklab
2024-10-12 0:13 ` |FAILURE| " dpdklab
2024-10-12 1:39 ` |PENDING| " dpdklab
2024-10-12 4:10 ` |SUCCESS| " dpdklab
2024-10-12 4:30 ` dpdklab
2024-10-12 19:42 ` dpdklab
2024-10-21 8:56 ` dpdklab
2024-10-23 5:42 ` dpdklab
2024-10-24 13:01 ` dpdklab
2024-10-24 13:05 ` dpdklab
2024-10-24 13:11 ` dpdklab
2024-10-24 13:13 ` dpdklab
2024-10-24 13:37 ` dpdklab
2024-10-25 8:13 ` dpdklab
2024-10-25 8:48 ` 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=202410111053.49BArhaN3981866@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).