From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139091-139092 [PATCH v2 2/2] test: add functional test for uuid
Date: Thu, 4 Apr 2024 05:55:01 +0800 [thread overview]
Message-ID: <202404032155.433Lt1A62023756@localhost.localdomain> (raw)
In-Reply-To: <20240403221319.499014-3-stephen@networkplumber.org>
Test-Label: loongarch-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/139092
_Unit Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wed, 3 Apr 2024 15:11:07 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139091-139092 --> 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/113 DPDK:fast-tests / acl_autotest OK 3.38s
2/113 DPDK:fast-tests / argparse_autotest OK 0.62s
3/113 DPDK:fast-tests / atomic_autotest OK 8.63s
4/113 DPDK:fast-tests / bitcount_autotest OK 0.32s
5/113 DPDK:fast-tests / bitmap_autotest OK 0.32s
6/113 DPDK:fast-tests / bitops_autotest OK 0.32s
7/113 DPDK:fast-tests / bitratestats_autotest OK 0.32s
8/113 DPDK:fast-tests / bpf_autotest OK 0.32s
9/113 DPDK:fast-tests / bpf_convert_autotest OK 0.32s
10/113 DPDK:fast-tests / byteorder_autotest OK 0.32s
11/113 DPDK:fast-tests / cksum_autotest OK 0.32s
12/113 DPDK:fast-tests / cmdline_autotest OK 0.32s
13/113 DPDK:fast-tests / common_autotest OK 1.17s
14/113 DPDK:fast-tests / compressdev_autotest SKIP 0.07s exit status 77
15/113 DPDK:fast-tests / cpuflags_autotest OK 0.32s
16/113 DPDK:fast-tests / crc_autotest OK 0.32s
17/113 DPDK:fast-tests / user_delay_us OK 0.32s
18/113 DPDK:fast-tests / debug_autotest OK 19.61s
19/113 DPDK:fast-tests / devargs_autotest OK 0.32s
20/113 DPDK:fast-tests / dispatcher_autotest OK 2.47s
21/113 DPDK:fast-tests / distributor_autotest OK 1.22s
22/113 DPDK:fast-tests / eal_flags_c_opt_autotest OK 1.17s
23/113 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.32s
24/113 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.27s
25/113 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.17s
26/113 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.32s
27/113 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.42s
28/113 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.37s
29/113 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.27s
30/113 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.27s
31/113 DPDK:fast-tests / eal_flags_mem_autotest OK 0.72s
32/113 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 22.31s
33/113 DPDK:fast-tests / eal_flags_misc_autotest OK 1.12s
34/113 DPDK:fast-tests / eal_fs_autotest OK 0.32s
35/113 DPDK:fast-tests / errno_autotest OK 0.32s
36/113 DPDK:fast-tests / ethdev_link_status OK 0.32s
37/113 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.72s
38/113 DPDK:fast-tests / event_ring_autotest OK 0.32s
39/113 DPDK:fast-tests / eventdev_common_autotest OK 0.32s
40/113 DPDK:fast-tests / eventdev_selftest_sw OK 7.33s
41/113 DPDK:fast-tests / fbarray_autotest OK 0.32s
42/113 DPDK:fast-tests / fib_autotest OK 1.02s
43/113 DPDK:fast-tests / fib6_autotest OK 1.07s
44/113 DPDK:fast-tests / func_reentrancy_autotest OK 2.48s
45/113 DPDK:fast-tests / graph_autotest OK 0.37s
46/113 DPDK:fast-tests / node_list_dump OK 0.32s
47/113 DPDK:fast-tests / hash_autotest OK 1.32s
48/113 DPDK:fast-tests / hash_readwrite_func_autotest OK 6.43s
49/113 DPDK:fast-tests / interrupt_autotest OK 1.62s
50/113 DPDK:fast-tests / ipfrag_autotest OK 0.12s
51/113 DPDK:fast-tests / ipsec_autotest SKIP 0.32s exit status 77
52/113 DPDK:fast-tests / kvargs_autotest OK 0.32s
53/113 DPDK:fast-tests / latencystats_autotest OK 0.32s
54/113 DPDK:fast-tests / lcores_autotest OK 5.13s
55/113 DPDK:fast-tests / logs_autotest OK 0.32s
56/113 DPDK:fast-tests / lpm_autotest OK 2.43s
57/113 DPDK:fast-tests / lpm6_autotest OK 5.59s
58/113 DPDK:fast-tests / malloc_autotest OK 58.04s
59/113 DPDK:fast-tests / mbuf_autotest OK 5.42s
60/113 DPDK:fast-tests / mcslock_autotest OK 2.72s
61/113 DPDK:fast-tests / member_autotest OK 1.52s
62/113 DPDK:fast-tests / memcpy_autotest OK 6.93s
63/113 DPDK:fast-tests / memory_autotest OK 0.12s
64/113 DPDK:fast-tests / mempool_autotest OK 0.47s
65/113 DPDK:fast-tests / memzone_autotest OK 0.17s
66/113 DPDK:fast-tests / meter_autotest OK 0.32s
67/113 DPDK:fast-tests / metrics_autotest OK 0.32s
68/113 DPDK:fast-tests / multiprocess_autotest OK 0.27s
69/113 DPDK:fast-tests / net_ether_autotest OK 1.02s
70/113 DPDK:fast-tests / pcapng_autotest OK 7.18s
71/113 DPDK:fast-tests / pdcp_autotest SKIP 0.07s exit status 77
72/113 DPDK:fast-tests / pdump_autotest OK 0.47s
73/113 DPDK:fast-tests / per_lcore_autotest OK 0.42s
74/113 DPDK:fast-tests / pflock_autotest OK 1.17s
75/113 DPDK:fast-tests / pie_autotest OK 0.42s
76/113 DPDK:fast-tests / ring_pmd_autotest OK 0.42s
77/113 DPDK:fast-tests / power_autotest OK 0.57s
78/113 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.07s exit status 77
79/113 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.32s exit status 77
80/113 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.07s exit status 77
81/113 DPDK:fast-tests / prefetch_autotest OK 0.42s
82/113 DPDK:fast-tests / rawdev_autotest OK 0.62s
83/113 DPDK:fast-tests / rcu_qsbr_autotest OK 1.17s
84/113 DPDK:fast-tests / reorder_autotest OK 0.67s
85/113 DPDK:fast-tests / rib_autotest OK 9.29s
86/113 DPDK:fast-tests / rib6_autotest OK 9.29s
87/113 DPDK:fast-tests / ring_autotest OK 0.67s
88/113 DPDK:fast-tests / rwlock_test1_autotest OK 1.37s
89/113 DPDK:fast-tests / rwlock_rda_autotest OK 5.63s
90/113 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.63s
91/113 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.63s
92/113 DPDK:fast-tests / sched_autotest OK 0.62s
93/113 DPDK:fast-tests / security_autotest OK 0.07s
94/113 DPDK:fast-tests / seqlock_autotest OK 2.32s
95/113 DPDK:fast-tests / service_autotest OK 3.07s
96/113 DPDK:fast-tests / spinlock_autotest OK 0.42s
97/113 DPDK:fast-tests / stack_autotest OK 0.87s
98/113 DPDK:fast-tests / stack_lf_autotest SKIP 0.07s exit status 77
99/113 DPDK:fast-tests / string_autotest OK 0.32s
100/113 DPDK:fast-tests / table_autotest OK 7.74s
101/113 DPDK:fast-tests / tailq_autotest OK 0.32s
102/113 DPDK:fast-tests / telemetry_data_autotest OK 0.32s
103/113 DPDK:fast-tests / telemetry_json_autotest OK 0.32s
104/113 DPDK:fast-tests / thash_autotest OK 0.32s
105/113 DPDK:fast-tests / threads_autotest OK 0.52s
106/113 DPDK:fast-tests / ticketlock_autotest OK 0.47s
107/113 DPDK:fast-tests / timer_autotest OK 3.92s
108/113 DPDK:fast-tests / trace_autotest OK 0.32s
109/113 DPDK:fast-tests / trace_autotest_with_traces OK 0.37s
110/113 DPDK:fast-tests / uuid_autotest OK 0.32s
111/113 DPDK:fast-tests / vdev_autotest OK 0.32s
112/113 DPDK:fast-tests / version_autotest OK 0.32s
113/113 DPDK:fast-tests / telemetry_all OK 1.27s
Ok: 106
Expected Fail: 0
Fail: 0
Unexpected Pass: 0
Skipped: 7
Timeout: 0
next prev parent reply other threads:[~2024-04-03 22:19 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240403221319.499014-3-stephen@networkplumber.org>
2024-04-03 21:50 ` qemudev
2024-04-03 21:55 ` qemudev [this message]
2024-04-03 22:13 ` |WARNING| pw139092 " checkpatch
2024-04-03 23:05 ` |FAILURE| " 0-day Robot
2024-04-03 23:13 ` |SUCCESS| pw139091-139092 [PATCH] [v2,2/2] test: add functional test dpdklab
2024-04-03 23:16 ` |FAILURE| " dpdklab
2024-04-03 23:17 ` |SUCCESS| " dpdklab
2024-04-03 23:17 ` |FAILURE| " dpdklab
2024-04-03 23:18 ` dpdklab
2024-04-03 23:18 ` |SUCCESS| " dpdklab
2024-04-03 23:18 ` dpdklab
2024-04-03 23:19 ` dpdklab
2024-04-03 23:19 ` dpdklab
2024-04-03 23:19 ` |FAILURE| " dpdklab
2024-04-03 23:19 ` dpdklab
2024-04-03 23:20 ` dpdklab
2024-04-03 23:20 ` |SUCCESS| " dpdklab
2024-04-03 23:23 ` dpdklab
2024-04-03 23:23 ` dpdklab
2024-04-03 23:23 ` dpdklab
2024-04-03 23:24 ` dpdklab
2024-04-03 23:24 ` dpdklab
2024-04-03 23:24 ` dpdklab
2024-04-03 23:24 ` dpdklab
2024-04-03 23:25 ` dpdklab
2024-04-03 23:25 ` dpdklab
2024-04-03 23:25 ` dpdklab
2024-04-03 23:25 ` dpdklab
2024-04-03 23:26 ` dpdklab
2024-04-03 23:26 ` dpdklab
2024-04-03 23:27 ` dpdklab
2024-04-03 23:27 ` dpdklab
2024-04-03 23:27 ` dpdklab
2024-04-03 23:28 ` dpdklab
2024-04-03 23:28 ` dpdklab
2024-04-03 23:29 ` dpdklab
2024-04-03 23:38 ` dpdklab
2024-04-03 23:38 ` dpdklab
2024-04-03 23:39 ` dpdklab
2024-04-03 23:39 ` |FAILURE| " dpdklab
2024-04-03 23:41 ` dpdklab
2024-04-03 23:44 ` |SUCCESS| " dpdklab
2024-04-03 23:44 ` dpdklab
2024-04-03 23:44 ` dpdklab
2024-04-03 23:45 ` |FAILURE| " dpdklab
2024-04-03 23:45 ` |SUCCESS| " dpdklab
2024-04-03 23:46 ` |FAILURE| " dpdklab
2024-04-03 23:46 ` |SUCCESS| " dpdklab
2024-04-03 23:46 ` dpdklab
2024-04-03 23:47 ` |FAILURE| " dpdklab
2024-04-03 23:47 ` dpdklab
2024-04-03 23:57 ` dpdklab
2024-04-03 23:57 ` dpdklab
2024-04-03 23:59 ` |SUCCESS| " dpdklab
2024-04-03 23:59 ` dpdklab
2024-04-04 0:00 ` |FAILURE| " dpdklab
2024-04-04 0:00 ` |SUCCESS| " dpdklab
2024-04-04 0:01 ` dpdklab
2024-04-04 0:01 ` |FAILURE| " dpdklab
2024-04-04 0:02 ` |SUCCESS| " dpdklab
2024-04-04 0:02 ` dpdklab
2024-04-04 0:02 ` dpdklab
2024-04-04 0:03 ` dpdklab
2024-04-04 0:04 ` dpdklab
2024-04-04 0:05 ` |FAILURE| " dpdklab
2024-04-04 0:12 ` dpdklab
2024-04-04 0:13 ` |SUCCESS| " dpdklab
2024-04-04 0:43 ` dpdklab
2024-04-04 0:44 ` dpdklab
2024-04-04 0:54 ` dpdklab
2024-04-04 0:58 ` dpdklab
2024-04-04 0:59 ` dpdklab
2024-04-04 1:02 ` dpdklab
2024-04-04 1:12 ` dpdklab
2024-04-04 1:14 ` dpdklab
2024-04-04 1:15 ` dpdklab
2024-04-04 1:16 ` dpdklab
2024-04-04 1:17 ` dpdklab
2024-04-04 1:17 ` dpdklab
2024-04-04 1:18 ` dpdklab
2024-04-04 1:20 ` dpdklab
2024-04-04 1:54 ` |FAILURE| " dpdklab
2024-04-04 1:57 ` dpdklab
2024-04-04 2:04 ` |SUCCESS| " dpdklab
2024-04-04 2:29 ` dpdklab
2024-04-04 11:57 ` dpdklab
2024-04-04 12:03 ` dpdklab
2024-04-04 12:07 ` dpdklab
2024-04-04 12:11 ` dpdklab
2024-04-04 12:15 ` 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=202404032155.433Lt1A62023756@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).