From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125195 [PATCH] app/testpmd: revert cleanup cleanly from signal
Date: Fri, 17 Mar 2023 01:26:18 +0800 [thread overview]
Message-ID: <202303161726.32GHQIsE594017@localhost.localdomain> (raw)
In-Reply-To: <20230316172739.77933-1-ferruh.yigit@amd.com>
Test-Label: loongarch-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/125195
_Unit Testing PASS_
Submitter: Ferruh Yigit <ferruh.yigit@amd.com>
Date: Thu, 16 Mar 2023 17:27:39 +0000
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 8880c07e04820eba0692cadb8764d1bbd09751a5
125195 --> 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/104 DPDK:fast-tests / acl_autotest OK 2.83s
2/104 DPDK:fast-tests / atomic_autotest OK 7.08s
3/104 DPDK:fast-tests / bitmap_autotest OK 0.07s
4/104 DPDK:fast-tests / bpf_autotest OK 0.07s
5/104 DPDK:fast-tests / bpf_convert_autotest OK 0.07s
6/104 DPDK:fast-tests / bitops_autotest OK 0.07s
7/104 DPDK:fast-tests / byteorder_autotest OK 0.07s
8/104 DPDK:fast-tests / cksum_autotest OK 0.07s
9/104 DPDK:fast-tests / cmdline_autotest OK 0.07s
10/104 DPDK:fast-tests / common_autotest OK 0.92s
11/104 DPDK:fast-tests / cpuflags_autotest OK 0.07s
12/104 DPDK:fast-tests / debug_autotest OK 1.42s
13/104 DPDK:fast-tests / devargs_autotest OK 0.07s
14/104 DPDK:fast-tests / eal_flags_c_opt_autotest OK 0.67s
15/104 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.22s
16/104 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.17s
17/104 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.12s
18/104 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.22s
19/104 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.27s
20/104 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.22s
21/104 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.17s
22/104 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.17s
23/104 DPDK:fast-tests / eal_flags_mem_autotest OK 0.52s
24/104 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 22.21s
25/104 DPDK:fast-tests / eal_flags_misc_autotest OK 0.77s
26/104 DPDK:fast-tests / eal_fs_autotest OK 0.07s
27/104 DPDK:fast-tests / errno_autotest OK 0.07s
28/104 DPDK:fast-tests / ethdev_link_status OK 0.07s
29/104 DPDK:fast-tests / event_ring_autotest OK 0.07s
30/104 DPDK:fast-tests / fib_autotest OK 0.87s
31/104 DPDK:fast-tests / fib6_autotest OK 0.87s
32/104 DPDK:fast-tests / func_reentrancy_autotest OK 2.28s
33/104 DPDK:fast-tests / hash_autotest OK 1.02s
34/104 DPDK:fast-tests / interrupt_autotest OK 1.37s
35/104 DPDK:fast-tests / ipfrag_autotest OK 0.07s
36/104 DPDK:fast-tests / lcores_autotest OK 1.07s
37/104 DPDK:fast-tests / logs_autotest OK 0.07s
38/104 DPDK:fast-tests / lpm_autotest OK 5.91s
39/104 DPDK:fast-tests / lpm6_autotest OK 8.82s
40/104 DPDK:fast-tests / malloc_autotest OK 60.40s
41/104 DPDK:fast-tests / mbuf_autotest OK 7.13s
42/104 DPDK:fast-tests / mcslock_autotest OK 4.33s
43/104 DPDK:fast-tests / memcpy_autotest OK 6.93s
44/104 DPDK:fast-tests / memory_autotest OK 0.12s
45/104 DPDK:fast-tests / mempool_autotest OK 0.47s
46/104 DPDK:fast-tests / memzone_autotest OK 0.17s
47/104 DPDK:fast-tests / meter_autotest OK 0.07s
48/104 DPDK:fast-tests / multiprocess_autotest OK 0.17s
49/104 DPDK:fast-tests / per_lcore_autotest OK 0.17s
50/104 DPDK:fast-tests / pflock_autotest OK 0.87s
51/104 DPDK:fast-tests / prefetch_autotest OK 0.07s
52/104 DPDK:fast-tests / rcu_qsbr_autotest OK 0.57s
53/104 DPDK:fast-tests / pie_autotest OK 0.07s
54/104 DPDK:fast-tests / rib_autotest OK 10.30s
55/104 DPDK:fast-tests / rib6_autotest OK 10.35s
56/104 DPDK:fast-tests / ring_autotest OK 0.12s
57/104 DPDK:fast-tests / rwlock_test1_autotest OK 0.82s
58/104 DPDK:fast-tests / rwlock_rda_autotest OK 5.08s
59/104 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.08s
60/104 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.08s
61/104 DPDK:fast-tests / sched_autotest OK 0.07s
62/104 DPDK:fast-tests / security_autotest OK 0.07s
63/104 DPDK:fast-tests / seqlock_autotest OK 2.07s
64/104 DPDK:fast-tests / spinlock_autotest OK 0.17s
65/104 DPDK:fast-tests / stack_autotest OK 0.87s
66/104 DPDK:fast-tests / stack_lf_autotest SKIP 0.07s exit status 77
67/104 DPDK:fast-tests / string_autotest OK 0.07s
68/104 DPDK:fast-tests / tailq_autotest OK 0.07s
69/104 DPDK:fast-tests / ticketlock_autotest OK 0.22s
70/104 DPDK:fast-tests / timer_autotest OK 3.87s
71/104 DPDK:fast-tests / user_delay_us OK 0.07s
72/104 DPDK:fast-tests / version_autotest OK 0.07s
73/104 DPDK:fast-tests / crc_autotest OK 0.07s
74/104 DPDK:fast-tests / distributor_autotest OK 1.22s
75/104 DPDK:fast-tests / eventdev_common_autotest OK 0.07s
76/104 DPDK:fast-tests / fbarray_autotest OK 0.07s
77/104 DPDK:fast-tests / hash_readwrite_func_autotest OK 6.44s
78/104 DPDK:fast-tests / ipsec_autotest SKIP 0.07s exit status 77
79/104 DPDK:fast-tests / kni_autotest SKIP 0.07s exit status 77
80/104 DPDK:fast-tests / kvargs_autotest OK 0.07s
81/104 DPDK:fast-tests / member_autotest OK 1.22s
82/104 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.07s exit status 77
83/104 DPDK:fast-tests / power_autotest OK 0.07s
84/104 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.07s exit status 77
85/104 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.07s exit status 77
86/104 DPDK:fast-tests / reorder_autotest OK 0.12s
87/104 DPDK:fast-tests / service_autotest OK 3.02s
88/104 DPDK:fast-tests / thash_autotest OK 0.07s
89/104 DPDK:fast-tests / threads_autotest OK 0.27s
90/104 DPDK:fast-tests / trace_autotest OK 0.07s
91/104 DPDK:fast-tests / trace_autotest_with_traces OK 0.12s
92/104 DPDK:fast-tests / metrics_autotest OK 0.07s
93/104 DPDK:fast-tests / telemetry_json_autotest OK 0.07s
94/104 DPDK:fast-tests / telemetry_data_autotest OK 0.07s
95/104 DPDK:fast-tests / table_autotest OK 10.11s
96/104 DPDK:fast-tests / ring_pmd_autotest OK 0.07s
97/104 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.47s
98/104 DPDK:fast-tests / bitratestats_autotest OK 0.07s
99/104 DPDK:fast-tests / latencystats_autotest OK 0.07s
100/104 DPDK:fast-tests / pdump_autotest OK 5.17s
101/104 DPDK:fast-tests / vdev_autotest OK 0.07s
102/104 DPDK:fast-tests / rawdev_autotest OK 0.07s
103/104 DPDK:fast-tests / compressdev_autotest SKIP 0.07s exit status 77
104/104 DPDK:fast-tests / telemetry_all OK 14.70s
Ok: 97
Expected Fail: 0
Fail: 0
Unexpected Pass: 0
Skipped: 7
Timeout: 0
next prev parent reply other threads:[~2023-03-16 17:40 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230316172739.77933-1-ferruh.yigit@amd.com>
2023-03-16 17:22 ` qemudev
2023-03-16 17:26 ` qemudev [this message]
2023-03-16 17:28 ` |WARNING| " checkpatch
2023-03-16 20:01 ` |SUCCESS| " 0-day Robot
2023-03-16 18:24 dpdklab
2023-03-16 18:31 dpdklab
2023-03-16 18:32 dpdklab
2023-03-16 18:34 dpdklab
2023-03-16 18:37 dpdklab
2023-03-16 18:43 dpdklab
2023-03-16 18:48 dpdklab
2023-03-16 18:48 dpdklab
2023-03-16 18:48 dpdklab
2023-03-16 18:53 dpdklab
2023-03-16 18:54 dpdklab
2023-03-16 19:00 dpdklab
2023-03-16 19:04 dpdklab
2023-03-16 19:06 dpdklab
2023-03-16 19:16 dpdklab
2023-03-16 19:17 dpdklab
2023-03-16 19:30 dpdklab
2023-03-16 19:33 dpdklab
2023-03-16 19:37 dpdklab
2023-03-16 19:42 dpdklab
2023-03-16 20:03 dpdklab
2023-03-16 20:08 dpdklab
2023-03-16 20:16 dpdklab
2023-03-16 20:21 dpdklab
2023-03-16 21:15 dpdklab
2023-03-16 21:28 dpdklab
2023-03-16 21:37 dpdklab
2023-03-16 22:08 dpdklab
2023-03-16 23:19 dpdklab
2023-03-16 23:40 dpdklab
2023-03-17 17:04 dpdklab
2023-03-17 17:09 dpdklab
2023-03-18 20:59 dpdklab
2023-03-18 21:58 dpdklab
2023-03-18 22:05 dpdklab
2023-03-18 22:12 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=202303161726.32GHQIsE594017@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).