From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139012-139013 [PATCH v1 2/2] deque: add unit tests for the deque library
Date: Mon, 1 Apr 2024 09:18:50 +0800 [thread overview]
Message-ID: <202404010118.4311IoEQ643264@localhost.localdomain> (raw)
In-Reply-To: <20240401013729.1466298-3-aditya.ambadipudi@arm.com>
Test-Label: loongarch-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/139013
_Unit Testing PASS_
Submitter: Aditya Ambadipudi <aditya.ambadipudi@arm.com>
Date: Sun, 31 Mar 2024 20:37:28 -0500
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: a9778aad62470a38ccbb4e09a2a6bf0cc2e0e36d
139012-139013 --> 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.08s
2/114 DPDK:fast-tests / argparse_autotest OK 0.37s
3/114 DPDK:fast-tests / atomic_autotest OK 8.43s
4/114 DPDK:fast-tests / bitcount_autotest OK 0.22s
5/114 DPDK:fast-tests / bitmap_autotest OK 0.22s
6/114 DPDK:fast-tests / bitops_autotest OK 0.22s
7/114 DPDK:fast-tests / bitratestats_autotest OK 0.22s
8/114 DPDK:fast-tests / bpf_autotest OK 0.22s
9/114 DPDK:fast-tests / bpf_convert_autotest OK 0.22s
10/114 DPDK:fast-tests / byteorder_autotest OK 0.22s
11/114 DPDK:fast-tests / cksum_autotest OK 0.22s
12/114 DPDK:fast-tests / cmdline_autotest OK 0.22s
13/114 DPDK:fast-tests / common_autotest OK 1.07s
14/114 DPDK:fast-tests / compressdev_autotest SKIP 0.07s exit status 77
15/114 DPDK:fast-tests / cpuflags_autotest OK 0.22s
16/114 DPDK:fast-tests / crc_autotest OK 0.22s
17/114 DPDK:fast-tests / user_delay_us OK 0.22s
18/114 DPDK:fast-tests / debug_autotest OK 20.66s
19/114 DPDK:fast-tests / deque_enqueue_dequeue_autotest OK 0.27s
20/114 DPDK:fast-tests / deque_helper_functions_autotest OK 0.22s
21/114 DPDK:fast-tests / devargs_autotest OK 0.22s
22/114 DPDK:fast-tests / dispatcher_autotest OK 2.42s
23/114 DPDK:fast-tests / distributor_autotest OK 1.22s
24/114 DPDK:fast-tests / eal_flags_c_opt_autotest OK 1.12s
25/114 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.32s
26/114 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.27s
27/114 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.17s
28/114 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.32s
29/114 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.42s
30/114 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.32s
31/114 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.27s
32/114 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.27s
33/114 DPDK:fast-tests / eal_flags_mem_autotest OK 0.72s
34/114 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 22.30s
35/114 DPDK:fast-tests / eal_flags_misc_autotest OK 1.12s
36/114 DPDK:fast-tests / eal_fs_autotest OK 0.22s
37/114 DPDK:fast-tests / errno_autotest OK 0.22s
38/114 DPDK:fast-tests / ethdev_link_status OK 0.22s
39/114 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.72s
40/114 DPDK:fast-tests / event_ring_autotest OK 0.22s
41/114 DPDK:fast-tests / eventdev_common_autotest OK 0.22s
42/114 DPDK:fast-tests / eventdev_selftest_sw OK 7.13s
43/114 DPDK:fast-tests / fbarray_autotest OK 0.22s
44/114 DPDK:fast-tests / fib_autotest OK 0.87s
45/114 DPDK:fast-tests / fib6_autotest OK 0.92s
46/114 DPDK:fast-tests / func_reentrancy_autotest OK 2.38s
47/114 DPDK:fast-tests / graph_autotest OK 0.58s
48/114 DPDK:fast-tests / node_list_dump OK 0.47s
49/114 DPDK:fast-tests / hash_autotest OK 1.37s
50/114 DPDK:fast-tests / hash_readwrite_func_autotest OK 6.44s
51/114 DPDK:fast-tests / interrupt_autotest OK 1.67s
52/114 DPDK:fast-tests / ipfrag_autotest OK 0.12s
53/114 DPDK:fast-tests / ipsec_autotest SKIP 0.47s exit status 77
54/114 DPDK:fast-tests / kvargs_autotest OK 0.47s
55/114 DPDK:fast-tests / latencystats_autotest OK 0.47s
56/114 DPDK:fast-tests / lcores_autotest OK 5.23s
57/114 DPDK:fast-tests / logs_autotest OK 0.47s
58/114 DPDK:fast-tests / lpm_autotest OK 2.48s
59/114 DPDK:fast-tests / lpm6_autotest OK 5.69s
60/114 DPDK:fast-tests / malloc_autotest OK 60.20s
61/114 DPDK:fast-tests / mbuf_autotest OK 5.13s
62/114 DPDK:fast-tests / mcslock_autotest OK 2.87s
63/114 DPDK:fast-tests / member_autotest OK 1.67s
64/114 DPDK:fast-tests / memcpy_autotest OK 7.08s
65/114 DPDK:fast-tests / memory_autotest OK 0.12s
66/114 DPDK:fast-tests / mempool_autotest OK 0.47s
67/114 DPDK:fast-tests / memzone_autotest OK 0.17s
68/114 DPDK:fast-tests / meter_autotest OK 0.57s
69/114 DPDK:fast-tests / metrics_autotest OK 0.47s
70/114 DPDK:fast-tests / multiprocess_autotest OK 0.27s
71/114 DPDK:fast-tests / net_ether_autotest OK 1.12s
72/114 DPDK:fast-tests / pcapng_autotest OK 6.93s
73/114 DPDK:fast-tests / pdcp_autotest SKIP 0.12s exit status 77
74/114 DPDK:fast-tests / pdump_autotest OK 0.57s
75/114 DPDK:fast-tests / per_lcore_autotest OK 0.57s
76/114 DPDK:fast-tests / pflock_autotest OK 1.27s
77/114 DPDK:fast-tests / pie_autotest OK 0.47s
78/114 DPDK:fast-tests / ring_pmd_autotest OK 0.47s
79/114 DPDK:fast-tests / power_autotest OK 0.47s
80/114 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.12s exit status 77
81/114 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.47s exit status 77
82/114 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.12s exit status 77
83/114 DPDK:fast-tests / prefetch_autotest OK 0.47s
84/114 DPDK:fast-tests / rawdev_autotest OK 0.47s
85/114 DPDK:fast-tests / rcu_qsbr_autotest OK 0.97s
86/114 DPDK:fast-tests / reorder_autotest OK 0.54s
87/114 DPDK:fast-tests / rib_autotest OK 9.14s
88/114 DPDK:fast-tests / rib6_autotest OK 9.12s
89/114 DPDK:fast-tests / ring_autotest OK 0.47s
90/114 DPDK:fast-tests / rwlock_test1_autotest OK 1.22s
91/114 DPDK:fast-tests / rwlock_rda_autotest OK 5.48s
92/114 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.48s
93/114 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.48s
94/114 DPDK:fast-tests / sched_autotest OK 0.47s
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.92s
100/114 DPDK:fast-tests / stack_lf_autotest SKIP 0.07s exit status 77
101/114 DPDK:fast-tests / string_autotest OK 0.47s
102/114 DPDK:fast-tests / table_autotest OK 7.84s
103/114 DPDK:fast-tests / tailq_autotest OK 0.47s
104/114 DPDK:fast-tests / telemetry_data_autotest OK 0.47s
105/114 DPDK:fast-tests / telemetry_json_autotest OK 0.47s
106/114 DPDK:fast-tests / thash_autotest OK 0.47s
107/114 DPDK:fast-tests / threads_autotest OK 0.62s
108/114 DPDK:fast-tests / ticketlock_autotest OK 0.67s
109/114 DPDK:fast-tests / timer_autotest OK 4.03s
110/114 DPDK:fast-tests / trace_autotest OK 0.47s
111/114 DPDK:fast-tests / trace_autotest_with_traces OK 0.47s
112/114 DPDK:fast-tests / vdev_autotest OK 0.47s
113/114 DPDK:fast-tests / version_autotest OK 0.47s
114/114 DPDK:fast-tests / telemetry_all OK 1.42s
Ok: 107
Expected Fail: 0
Fail: 0
Unexpected Pass: 0
Skipped: 7
Timeout: 0
next prev parent reply other threads:[~2024-04-01 1:43 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240401013729.1466298-3-aditya.ambadipudi@arm.com>
2024-04-01 1:14 ` qemudev
2024-04-01 1:18 ` qemudev [this message]
2024-04-01 1:38 ` |WARNING| pw139013 " checkpatch
2024-04-01 2:17 ` |SUCCESS| pw139012-139013 [PATCH] [v1,2/2] deque: add unit tests for dpdklab
2024-04-01 2:17 ` dpdklab
2024-04-01 2:17 ` dpdklab
2024-04-01 2:17 ` dpdklab
2024-04-01 2:18 ` dpdklab
2024-04-01 2:18 ` dpdklab
2024-04-01 2:18 ` dpdklab
2024-04-01 2:19 ` dpdklab
2024-04-01 2:19 ` dpdklab
2024-04-01 2:19 ` dpdklab
2024-04-01 2:19 ` dpdklab
2024-04-01 2:20 ` dpdklab
2024-04-01 2:20 ` dpdklab
2024-04-01 2:20 ` dpdklab
2024-04-01 2:20 ` dpdklab
2024-04-01 2:20 ` dpdklab
2024-04-01 2:21 ` dpdklab
2024-04-01 2:21 ` dpdklab
2024-04-01 2:21 ` dpdklab
2024-04-01 2:21 ` dpdklab
2024-04-01 2:21 ` dpdklab
2024-04-01 2:22 ` dpdklab
2024-04-01 2:22 ` dpdklab
2024-04-01 2:22 ` dpdklab
2024-04-01 2:23 ` dpdklab
2024-04-01 2:23 ` dpdklab
2024-04-01 2:24 ` dpdklab
2024-04-01 2:24 ` dpdklab
2024-04-01 2:25 ` dpdklab
2024-04-01 2:25 ` dpdklab
2024-04-01 2:25 ` dpdklab
2024-04-01 2:26 ` dpdklab
2024-04-01 2:26 ` dpdklab
2024-04-01 2:26 ` dpdklab
2024-04-01 2:26 ` dpdklab
2024-04-01 2:27 ` dpdklab
2024-04-01 2:27 ` dpdklab
2024-04-01 2:28 ` dpdklab
2024-04-01 2:28 ` dpdklab
2024-04-01 2:29 ` dpdklab
2024-04-01 2:29 ` dpdklab
2024-04-01 2:31 ` dpdklab
2024-04-01 2:31 ` dpdklab
2024-04-01 2:31 ` dpdklab
2024-04-01 2:32 ` dpdklab
2024-04-01 2:32 ` dpdklab
2024-04-01 2:33 ` dpdklab
2024-04-01 2:33 ` dpdklab
2024-04-01 2:33 ` dpdklab
2024-04-01 2:33 ` dpdklab
2024-04-01 2:34 ` dpdklab
2024-04-01 2:34 ` dpdklab
2024-04-01 2:34 ` dpdklab
2024-04-01 2:36 ` dpdklab
2024-04-01 2:36 ` dpdklab
2024-04-01 2:36 ` dpdklab
2024-04-01 2:37 ` dpdklab
2024-04-01 2:38 ` dpdklab
2024-04-01 2:38 ` dpdklab
2024-04-01 2:38 ` dpdklab
2024-04-01 2:40 ` dpdklab
2024-04-01 2:40 ` dpdklab
2024-04-01 2:41 ` dpdklab
2024-04-01 2:42 ` dpdklab
2024-04-01 2:44 ` dpdklab
2024-04-01 2:45 ` dpdklab
2024-04-01 2:45 ` dpdklab
2024-04-01 2:47 ` dpdklab
2024-04-01 2:48 ` dpdklab
2024-04-01 2:48 ` dpdklab
2024-04-01 2:53 ` dpdklab
2024-04-01 2:56 ` dpdklab
2024-04-01 2:57 ` dpdklab
2024-04-01 2:57 ` dpdklab
2024-04-01 2:57 ` dpdklab
2024-04-01 2:58 ` dpdklab
2024-04-01 3:02 ` dpdklab
2024-04-01 3:05 ` dpdklab
2024-04-01 3:14 ` dpdklab
2024-04-01 3:32 ` dpdklab
2024-04-01 3:34 ` dpdklab
2024-04-01 4:25 ` |FAILURE| pw139013 [PATCH v1 2/2] deque: add unit tests for the deque library 0-day Robot
2024-04-03 10:10 ` |SUCCESS| pw139012-139013 [PATCH] [v1,2/2] deque: add unit tests for dpdklab
2024-04-03 10:13 ` dpdklab
2024-04-03 10:30 ` dpdklab
2024-04-03 10:31 ` dpdklab
2024-04-03 10:35 ` 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=202404010118.4311IoEQ643264@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).