From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw135761 [PATCH] doc: fix test eventdev example commands
Date: Fri, 5 Jan 2024 23:40:26 +0800 [thread overview]
Message-ID: <202401051540.405FeQwe2374448@localhost.localdomain> (raw)
In-Reply-To: <20240105155431.5639-1-pbhagavatula@marvell.com>
Test-Label: loongarch-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135761
_Unit Testing PASS_
Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Fri, 5 Jan 2024 21:24:31 +0530
DPDK git baseline: Repo:dpdk-next-eventdev
Branch: for-main
CommitID: a1dff49b89249659bb40512bb1410a9afba0f382
135761 --> 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/111 DPDK:fast-tests / acl_autotest OK 3.28s
2/111 DPDK:fast-tests / atomic_autotest OK 6.83s
3/111 DPDK:fast-tests / bitcount_autotest OK 0.22s
4/111 DPDK:fast-tests / bitmap_autotest OK 0.22s
5/111 DPDK:fast-tests / bitops_autotest OK 0.22s
6/111 DPDK:fast-tests / bitratestats_autotest OK 0.22s
7/111 DPDK:fast-tests / bpf_autotest OK 0.22s
8/111 DPDK:fast-tests / bpf_convert_autotest OK 0.22s
9/111 DPDK:fast-tests / byteorder_autotest OK 0.22s
10/111 DPDK:fast-tests / cksum_autotest OK 0.22s
11/111 DPDK:fast-tests / cmdline_autotest OK 0.22s
12/111 DPDK:fast-tests / common_autotest OK 1.07s
13/111 DPDK:fast-tests / compressdev_autotest SKIP 0.07s exit status 77
14/111 DPDK:fast-tests / cpuflags_autotest OK 0.22s
15/111 DPDK:fast-tests / crc_autotest OK 0.22s
16/111 DPDK:fast-tests / user_delay_us OK 0.22s
17/111 DPDK:fast-tests / debug_autotest OK 13.45s
18/111 DPDK:fast-tests / devargs_autotest OK 0.37s
19/111 DPDK:fast-tests / dispatcher_autotest OK 2.47s
20/111 DPDK:fast-tests / distributor_autotest OK 1.27s
21/111 DPDK:fast-tests / eal_flags_c_opt_autotest OK 1.17s
22/111 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.32s
23/111 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.27s
24/111 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.17s
25/111 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.32s
26/111 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.42s
27/111 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.37s
28/111 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.27s
29/111 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.27s
30/111 DPDK:fast-tests / eal_flags_mem_autotest OK 0.77s
31/111 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 22.41s
32/111 DPDK:fast-tests / eal_flags_misc_autotest OK 1.17s
33/111 DPDK:fast-tests / eal_fs_autotest OK 0.32s
34/111 DPDK:fast-tests / errno_autotest OK 0.32s
35/111 DPDK:fast-tests / ethdev_link_status OK 0.32s
36/111 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.72s
37/111 DPDK:fast-tests / event_ring_autotest OK 0.32s
38/111 DPDK:fast-tests / eventdev_common_autotest OK 0.32s
39/111 DPDK:fast-tests / eventdev_selftest_sw OK 7.33s
40/111 DPDK:fast-tests / fbarray_autotest OK 0.32s
41/111 DPDK:fast-tests / fib_autotest OK 1.02s
42/111 DPDK:fast-tests / fib6_autotest OK 1.02s
43/111 DPDK:fast-tests / func_reentrancy_autotest OK 2.13s
44/111 DPDK:fast-tests / graph_autotest OK 0.37s
45/111 DPDK:fast-tests / node_list_dump OK 0.32s
46/111 DPDK:fast-tests / hash_autotest OK 1.27s
47/111 DPDK:fast-tests / hash_readwrite_func_autotest OK 6.48s
48/111 DPDK:fast-tests / interrupt_autotest OK 1.62s
49/111 DPDK:fast-tests / ipfrag_autotest OK 0.12s
50/111 DPDK:fast-tests / ipsec_autotest SKIP 0.37s exit status 77
51/111 DPDK:fast-tests / kvargs_autotest OK 0.37s
52/111 DPDK:fast-tests / latencystats_autotest OK 0.37s
53/111 DPDK:fast-tests / lcores_autotest OK 5.38s
54/111 DPDK:fast-tests / logs_autotest OK 0.32s
55/111 DPDK:fast-tests / lpm_autotest OK 2.43s
56/111 DPDK:fast-tests / lpm6_autotest OK 5.59s
57/111 DPDK:fast-tests / malloc_autotest OK 64.90s
58/111 DPDK:fast-tests / mbuf_autotest OK 4.82s
59/111 DPDK:fast-tests / mcslock_autotest OK 2.97s
60/111 DPDK:fast-tests / member_autotest OK 1.52s
61/111 DPDK:fast-tests / memcpy_autotest OK 7.23s
62/111 DPDK:fast-tests / memory_autotest OK 0.12s
63/111 DPDK:fast-tests / mempool_autotest OK 0.47s
64/111 DPDK:fast-tests / memzone_autotest OK 0.17s
65/111 DPDK:fast-tests / meter_autotest OK 0.32s
66/111 DPDK:fast-tests / metrics_autotest OK 0.32s
67/111 DPDK:fast-tests / multiprocess_autotest OK 0.27s
68/111 DPDK:fast-tests / net_ether_autotest OK 1.02s
69/111 DPDK:fast-tests / pcapng_autotest OK 6.93s
70/111 DPDK:fast-tests / pdcp_autotest SKIP 0.07s exit status 77
71/111 DPDK:fast-tests / pdump_autotest OK 0.47s
72/111 DPDK:fast-tests / per_lcore_autotest OK 0.42s
73/111 DPDK:fast-tests / pflock_autotest OK 1.17s
74/111 DPDK:fast-tests / pie_autotest OK 0.37s
75/111 DPDK:fast-tests / ring_pmd_autotest OK 0.37s
76/111 DPDK:fast-tests / power_autotest OK 0.32s
77/111 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.07s exit status 77
78/111 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.32s exit status 77
79/111 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.07s exit status 77
80/111 DPDK:fast-tests / prefetch_autotest OK 0.32s
81/111 DPDK:fast-tests / rawdev_autotest OK 0.32s
82/111 DPDK:fast-tests / rcu_qsbr_autotest OK 0.87s
83/111 DPDK:fast-tests / reorder_autotest OK 0.42s
84/111 DPDK:fast-tests / rib_autotest OK 8.99s
85/111 DPDK:fast-tests / rib6_autotest OK 8.98s
86/111 DPDK:fast-tests / ring_autotest OK 0.37s
87/111 DPDK:fast-tests / rwlock_test1_autotest OK 1.12s
88/111 DPDK:fast-tests / rwlock_rda_autotest OK 5.33s
89/111 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.58s
90/111 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.33s
91/111 DPDK:fast-tests / sched_autotest OK 0.32s
92/111 DPDK:fast-tests / security_autotest OK 0.12s
93/111 DPDK:fast-tests / seqlock_autotest OK 2.32s
94/111 DPDK:fast-tests / service_autotest OK 3.07s
95/111 DPDK:fast-tests / spinlock_autotest OK 0.67s
96/111 DPDK:fast-tests / stack_autotest OK 0.92s
97/111 DPDK:fast-tests / stack_lf_autotest SKIP 0.07s exit status 77
98/111 DPDK:fast-tests / string_autotest OK 0.32s
99/111 DPDK:fast-tests / table_autotest OK 7.89s
100/111 DPDK:fast-tests / tailq_autotest OK 0.32s
101/111 DPDK:fast-tests / telemetry_data_autotest OK 0.37s
102/111 DPDK:fast-tests / telemetry_json_autotest OK 0.32s
103/111 DPDK:fast-tests / thash_autotest OK 0.37s
104/111 DPDK:fast-tests / threads_autotest OK 0.52s
105/111 DPDK:fast-tests / ticketlock_autotest OK 0.52s
106/111 DPDK:fast-tests / timer_autotest OK 3.92s
107/111 DPDK:fast-tests / trace_autotest OK 0.32s
108/111 DPDK:fast-tests / trace_autotest_with_traces OK 0.37s
109/111 DPDK:fast-tests / vdev_autotest OK 0.32s
110/111 DPDK:fast-tests / version_autotest OK 0.32s
111/111 DPDK:fast-tests / telemetry_all OK 1.32s
Ok: 104
Expected Fail: 0
Fail: 0
Unexpected Pass: 0
Skipped: 7
Timeout: 0
next prev parent reply other threads:[~2024-01-05 16:01 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240105155431.5639-1-pbhagavatula@marvell.com>
2024-01-05 15:36 ` qemudev
2024-01-05 15:40 ` qemudev [this message]
2024-01-05 15:55 ` checkpatch
2024-01-05 17:12 ` 0-day Robot
2024-01-06 0:35 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2024-01-05 20:02 dpdklab
2024-01-05 18:13 dpdklab
2024-01-05 18:00 dpdklab
2024-01-05 17:59 dpdklab
2024-01-05 17:54 dpdklab
2024-01-05 17:50 dpdklab
2024-01-05 17:50 dpdklab
2024-01-05 17:50 dpdklab
2024-01-05 17:47 dpdklab
2024-01-05 17:46 dpdklab
2024-01-05 17:23 dpdklab
2024-01-05 17:16 dpdklab
2024-01-05 17:16 dpdklab
2024-01-05 17:14 dpdklab
2024-01-05 17:11 dpdklab
2024-01-05 17:10 dpdklab
2024-01-05 17:10 dpdklab
2024-01-05 17:10 dpdklab
2024-01-05 17:09 dpdklab
2024-01-05 17:09 dpdklab
2024-01-05 17:06 dpdklab
2024-01-05 17:06 dpdklab
2024-01-05 17:06 dpdklab
2024-01-05 17:06 dpdklab
2024-01-05 17:06 dpdklab
2024-01-05 17:05 dpdklab
2024-01-05 17:05 dpdklab
2024-01-05 17:05 dpdklab
2024-01-05 17:05 dpdklab
2024-01-05 17:05 dpdklab
2024-01-05 17:05 dpdklab
2024-01-05 17:05 dpdklab
2024-01-05 17:04 dpdklab
2024-01-05 17:04 dpdklab
2024-01-05 17:01 dpdklab
2024-01-05 17:01 dpdklab
2024-01-05 17:01 dpdklab
2024-01-05 16:59 dpdklab
2024-01-05 16:59 dpdklab
2024-01-05 16:59 dpdklab
2024-01-05 16:59 dpdklab
2024-01-05 16:59 dpdklab
2024-01-05 16:59 dpdklab
2024-01-05 16:59 dpdklab
2024-01-05 16:58 dpdklab
2024-01-05 16:58 dpdklab
2024-01-05 16:58 dpdklab
2024-01-05 16:58 dpdklab
2024-01-05 16:57 dpdklab
2024-01-05 16:57 dpdklab
2024-01-05 16:57 dpdklab
2024-01-05 16:57 dpdklab
2024-01-05 16:57 dpdklab
2024-01-05 16:56 dpdklab
2024-01-05 16:56 dpdklab
2024-01-05 16:55 dpdklab
2024-01-05 16:55 dpdklab
2024-01-05 16:54 dpdklab
2024-01-05 16:53 dpdklab
2024-01-05 16:52 dpdklab
2024-01-05 16:46 dpdklab
2024-01-05 16:46 dpdklab
2024-01-05 16:45 dpdklab
2024-01-05 16:45 dpdklab
2024-01-05 16:45 dpdklab
2024-01-05 16:44 dpdklab
2024-01-05 16:44 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=202401051540.405FeQwe2374448@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).