From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw153872-153874 [PATCH v2 3/3] app/eventdev: add vector adapter performance test
Date: Fri, 30 May 2025 05:56:09 +0800 [thread overview]
Message-ID: <202505292156.54TLu95H3757311@localhost.localdomain> (raw)
In-Reply-To: <20250529222437.91818-4-pbhagavatula@marvell.com>
Test-Label: loongarch-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/153874
_Unit Testing PASS_
Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Fri, 30 May 2025 03:54:35 +0530
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: a633a128fd09ff1fc72312f4e4d1a9e0f73aa359
153872-153874 --> 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.26s
2/120 DPDK:fast-tests / alarm_autotest OK 1.54s
3/120 DPDK:fast-tests / argparse_autotest OK 0.53s
4/120 DPDK:fast-tests / atomic_autotest OK 6.91s
5/120 DPDK:fast-tests / bitcount_autotest OK 0.43s
6/120 DPDK:fast-tests / bitmap_autotest OK 0.43s
7/120 DPDK:fast-tests / bitops_autotest OK 1.93s
8/120 DPDK:fast-tests / bitratestats_autotest OK 0.43s
9/120 DPDK:fast-tests / bitset_autotest OK 3.16s
10/120 DPDK:fast-tests / bpf_autotest OK 0.44s
11/120 DPDK:fast-tests / bpf_convert_autotest OK 0.44s
12/120 DPDK:fast-tests / byteorder_autotest OK 0.43s
13/120 DPDK:fast-tests / cfgfile_autotest OK 0.43s
14/120 DPDK:fast-tests / cksum_autotest OK 0.43s
15/120 DPDK:fast-tests / cmdline_autotest OK 0.43s
16/120 DPDK:fast-tests / common_autotest OK 1.32s
17/120 DPDK:fast-tests / compressdev_autotest SKIP 0.07s exit status 77
18/120 DPDK:fast-tests / cpuflags_autotest OK 0.43s
19/120 DPDK:fast-tests / crc_autotest OK 0.43s
20/120 DPDK:fast-tests / user_delay_us OK 0.43s
21/120 DPDK:fast-tests / debug_autotest OK 20.68s
22/120 DPDK:fast-tests / devargs_autotest OK 0.43s
23/120 DPDK:fast-tests / dispatcher_autotest OK 2.57s
24/120 DPDK:fast-tests / distributor_autotest OK 1.20s
25/120 DPDK:fast-tests / eal_flags_c_opt_autotest OK 0.76s
26/120 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.22s
27/120 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.20s
28/120 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.13s
29/120 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.22s
30/120 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.30s
31/120 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.25s
32/120 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.20s
33/120 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.19s
34/120 DPDK:fast-tests / eal_flags_mem_autotest OK 0.59s
35/120 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 22.22s
36/120 DPDK:fast-tests / eal_flags_misc_autotest OK 1.03s
37/120 DPDK:fast-tests / eal_fs_autotest OK 0.43s
38/120 DPDK:fast-tests / errno_autotest OK 0.43s
39/120 DPDK:fast-tests / ethdev_link_status OK 0.43s
40/120 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.69s
41/120 DPDK:fast-tests / event_ring_autotest OK 0.43s
42/120 DPDK:fast-tests / event_vector_adapter_autotest OK 2.49s
43/120 DPDK:fast-tests / eventdev_common_autotest OK 0.43s
44/120 DPDK:fast-tests / eventdev_selftest_sw OK 7.26s
45/120 DPDK:fast-tests / fbarray_autotest OK 0.43s
46/120 DPDK:fast-tests / fib_autotest OK 1.27s
47/120 DPDK:fast-tests / fib6_autotest OK 1.06s
48/120 DPDK:fast-tests / func_reentrancy_autotest OK 2.28s
49/120 DPDK:fast-tests / graph_autotest OK 0.43s
50/120 DPDK:fast-tests / node_list_dump OK 0.43s
51/120 DPDK:fast-tests / hash_autotest OK 1.05s
52/120 DPDK:fast-tests / hash_readwrite_func_autotest OK 6.40s
53/120 DPDK:fast-tests / interrupt_autotest OK 1.73s
54/120 DPDK:fast-tests / ipfrag_autotest OK 0.08s
55/120 DPDK:fast-tests / ipsec_autotest SKIP 0.43s exit status 77
56/120 DPDK:fast-tests / kvargs_autotest OK 0.44s
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.24s
60/120 DPDK:fast-tests / logs_autotest OK 0.43s
61/120 DPDK:fast-tests / lpm_autotest OK 2.47s
62/120 DPDK:fast-tests / lpm6_autotest OK 5.59s
63/120 DPDK:fast-tests / malloc_autotest OK 60.64s
64/120 DPDK:fast-tests / mbuf_autotest OK 5.57s
65/120 DPDK:fast-tests / mcslock_autotest OK 4.19s
66/120 DPDK:fast-tests / member_autotest OK 1.65s
67/120 DPDK:fast-tests / memcpy_autotest OK 6.95s
68/120 DPDK:fast-tests / memory_autotest OK 0.09s
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.43s
72/120 DPDK:fast-tests / metrics_autotest OK 0.43s
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.91s
77/120 DPDK:fast-tests / pdcp_autotest SKIP 0.07s exit status 77
78/120 DPDK:fast-tests / pdump_autotest OK 0.55s
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.43s 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.43s
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.49s
92/120 DPDK:fast-tests / rib_autotest OK 9.08s
93/120 DPDK:fast-tests / rib6_autotest OK 9.07s
94/120 DPDK:fast-tests / ring_autotest OK 0.46s
95/120 DPDK:fast-tests / rwlock_test1_autotest OK 1.18s
96/120 DPDK:fast-tests / rwlock_rda_autotest OK 5.43s
97/120 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.43s
98/120 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.43s
99/120 DPDK:fast-tests / sched_autotest OK 0.43s
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.14s
103/120 DPDK:fast-tests / soring_autotest OK 0.44s
104/120 DPDK:fast-tests / spinlock_autotest OK 0.51s
105/120 DPDK:fast-tests / stack_autotest OK 0.87s
106/120 DPDK:fast-tests / stack_lf_autotest SKIP 0.06s exit status 77
107/120 DPDK:fast-tests / string_autotest OK 0.43s
108/120 DPDK:fast-tests / table_autotest OK 7.87s
109/120 DPDK:fast-tests / tailq_autotest OK 0.43s
110/120 DPDK:fast-tests / telemetry_data_autotest OK 0.44s
111/120 DPDK:fast-tests / telemetry_json_autotest OK 0.43s
112/120 DPDK:fast-tests / thash_autotest OK 0.44s
113/120 DPDK:fast-tests / threads_autotest OK 0.61s
114/120 DPDK:fast-tests / ticketlock_autotest OK 0.60s
115/120 DPDK:fast-tests / timer_autotest OK 3.93s
116/120 DPDK:fast-tests / trace_autotest OK 0.43s
117/120 DPDK:fast-tests / trace_autotest_with_traces OK 0.44s
118/120 DPDK:fast-tests / vdev_autotest OK 0.43s
119/120 DPDK:fast-tests / version_autotest OK 0.43s
120/120 DPDK:fast-tests / telemetry_all OK 1.35s
Ok: 113
Expected Fail: 0
Fail: 0
Unexpected Pass: 0
Skipped: 7
Timeout: 0
next prev parent reply other threads:[~2025-05-29 22:32 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250529222437.91818-4-pbhagavatula@marvell.com>
2025-05-29 21:51 ` qemudev
2025-05-29 21:56 ` qemudev [this message]
2025-05-29 22:25 ` |SUCCESS| pw153874 " checkpatch
2025-05-29 23:44 ` 0-day Robot
2025-05-30 5:12 ` |SUCCESS| pw153872-153874 [PATCH] [v2,3/3] app/eventdev: add vector dpdklab
2025-05-30 6:39 ` |PENDING| " dpdklab
2025-05-30 6:42 ` dpdklab
2025-05-30 7:12 ` dpdklab
2025-05-30 7:14 ` |SUCCESS| " dpdklab
2025-05-30 7:24 ` |PENDING| " dpdklab
2025-05-30 8:12 ` |SUCCESS| " dpdklab
2025-05-30 8:13 ` dpdklab
2025-05-30 8:14 ` dpdklab
2025-05-30 8:15 ` dpdklab
2025-05-30 8:15 ` dpdklab
2025-05-30 8:16 ` dpdklab
2025-05-30 8:17 ` dpdklab
2025-05-30 9:20 ` |PENDING| " dpdklab
2025-05-30 9:46 ` |WARNING| " dpdklab
2025-05-30 9:47 ` dpdklab
2025-05-30 9:49 ` dpdklab
2025-05-30 9:49 ` dpdklab
2025-05-30 9:50 ` dpdklab
2025-05-30 9:51 ` dpdklab
2025-05-30 13:53 ` dpdklab
2025-05-30 17:44 ` |SUCCESS| " dpdklab
2025-05-30 17:53 ` dpdklab
2025-05-30 22:54 ` |WARNING| " dpdklab
2025-05-30 23:01 ` dpdklab
2025-05-31 4:16 ` |SUCCESS| " dpdklab
2025-05-31 6:05 ` dpdklab
2025-05-31 6:38 ` dpdklab
2025-06-04 15:11 ` 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=202505292156.54TLu95H3757311@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).