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