From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140183 [PATCH v1] net/cpfl: get running host ID for CPFL PMD
Date: Mon, 20 May 2024 12:22:12 +0800 [thread overview]
Message-ID: <202405200422.44K4MC10120723@localhost.localdomain> (raw)
In-Reply-To: <20240520044415.2307157-1-shaiq.wani@intel.com>
Test-Label: loongarch-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/140183
_Unit Testing PASS_
Submitter: Shaiq Wani <shaiq.wani@intel.com>
Date: Mon, 20 May 2024 04:44:15 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 2ac57ed414af92f0c30a799e1824fd47f86a94b0
140183 --> 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/112 DPDK:fast-tests / acl_autotest OK 3.38s
2/112 DPDK:fast-tests / argparse_autotest OK 0.62s
3/112 DPDK:fast-tests / atomic_autotest OK 8.83s
4/112 DPDK:fast-tests / bitcount_autotest OK 0.47s
5/112 DPDK:fast-tests / bitmap_autotest OK 0.47s
6/112 DPDK:fast-tests / bitops_autotest OK 0.47s
7/112 DPDK:fast-tests / bitratestats_autotest OK 0.47s
8/112 DPDK:fast-tests / bpf_autotest OK 0.47s
9/112 DPDK:fast-tests / bpf_convert_autotest OK 0.47s
10/112 DPDK:fast-tests / byteorder_autotest OK 0.47s
11/112 DPDK:fast-tests / cksum_autotest OK 0.47s
12/112 DPDK:fast-tests / cmdline_autotest OK 0.47s
13/112 DPDK:fast-tests / common_autotest OK 1.32s
14/112 DPDK:fast-tests / compressdev_autotest SKIP 0.12s exit status 77
15/112 DPDK:fast-tests / cpuflags_autotest OK 0.47s
16/112 DPDK:fast-tests / crc_autotest OK 0.47s
17/112 DPDK:fast-tests / user_delay_us OK 0.47s
18/112 DPDK:fast-tests / debug_autotest OK 22.23s
19/112 DPDK:fast-tests / devargs_autotest OK 0.47s
20/112 DPDK:fast-tests / dispatcher_autotest OK 2.47s
21/112 DPDK:fast-tests / distributor_autotest OK 1.27s
22/112 DPDK:fast-tests / eal_flags_c_opt_autotest OK 1.12s
23/112 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.32s
24/112 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.27s
25/112 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.17s
26/112 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.32s
27/112 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.42s
28/112 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.37s
29/112 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.27s
30/112 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.27s
31/112 DPDK:fast-tests / eal_flags_mem_autotest OK 0.72s
32/112 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 22.36s
33/112 DPDK:fast-tests / eal_flags_misc_autotest OK 1.12s
34/112 DPDK:fast-tests / eal_fs_autotest OK 0.47s
35/112 DPDK:fast-tests / errno_autotest OK 0.47s
36/112 DPDK:fast-tests / ethdev_link_status OK 0.47s
37/112 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.72s
38/112 DPDK:fast-tests / event_ring_autotest OK 0.47s
39/112 DPDK:fast-tests / eventdev_common_autotest OK 0.47s
40/112 DPDK:fast-tests / eventdev_selftest_sw OK 7.38s
41/112 DPDK:fast-tests / fbarray_autotest OK 0.47s
42/112 DPDK:fast-tests / fib_autotest OK 1.17s
43/112 DPDK:fast-tests / fib6_autotest OK 1.22s
44/112 DPDK:fast-tests / func_reentrancy_autotest OK 2.48s
45/112 DPDK:fast-tests / graph_autotest OK 0.47s
46/112 DPDK:fast-tests / node_list_dump OK 0.47s
47/112 DPDK:fast-tests / hash_autotest OK 1.42s
48/112 DPDK:fast-tests / hash_readwrite_func_autotest OK 6.48s
49/112 DPDK:fast-tests / interrupt_autotest OK 1.77s
50/112 DPDK:fast-tests / ipfrag_autotest OK 0.12s
51/112 DPDK:fast-tests / ipsec_autotest SKIP 0.47s exit status 77
52/112 DPDK:fast-tests / kvargs_autotest OK 0.47s
53/112 DPDK:fast-tests / latencystats_autotest OK 0.47s
54/112 DPDK:fast-tests / lcores_autotest OK 5.28s
55/112 DPDK:fast-tests / logs_autotest OK 0.47s
56/112 DPDK:fast-tests / lpm_autotest OK 2.53s
57/112 DPDK:fast-tests / lpm6_autotest OK 5.69s
58/112 DPDK:fast-tests / malloc_autotest OK 61.86s
59/112 DPDK:fast-tests / mbuf_autotest OK 5.12s
60/112 DPDK:fast-tests / mcslock_autotest OK 3.02s
61/112 DPDK:fast-tests / member_autotest OK 1.77s
62/112 DPDK:fast-tests / memcpy_autotest OK 7.08s
63/112 DPDK:fast-tests / memory_autotest OK 0.12s
64/112 DPDK:fast-tests / mempool_autotest OK 0.47s
65/112 DPDK:fast-tests / memzone_autotest OK 0.17s
66/112 DPDK:fast-tests / meter_autotest OK 0.47s
67/112 DPDK:fast-tests / metrics_autotest OK 0.47s
68/112 DPDK:fast-tests / multiprocess_autotest OK 0.27s
69/112 DPDK:fast-tests / net_ether_autotest OK 1.12s
70/112 DPDK:fast-tests / pcapng_autotest OK 6.18s
71/112 DPDK:fast-tests / pdcp_autotest SKIP 0.12s exit status 77
72/112 DPDK:fast-tests / pdump_autotest OK 0.57s
73/112 DPDK:fast-tests / per_lcore_autotest OK 0.57s
74/112 DPDK:fast-tests / pflock_autotest OK 1.27s
75/112 DPDK:fast-tests / pie_autotest OK 0.47s
76/112 DPDK:fast-tests / ring_pmd_autotest OK 0.47s
77/112 DPDK:fast-tests / power_autotest OK 0.47s
78/112 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.12s exit status 77
79/112 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.47s exit status 77
80/112 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.12s exit status 77
81/112 DPDK:fast-tests / prefetch_autotest OK 0.47s
82/112 DPDK:fast-tests / rawdev_autotest OK 0.47s
83/112 DPDK:fast-tests / rcu_qsbr_autotest OK 0.97s
84/112 DPDK:fast-tests / reorder_autotest OK 0.52s
85/112 DPDK:fast-tests / rib_autotest OK 9.24s
86/112 DPDK:fast-tests / rib6_autotest OK 9.24s
87/112 DPDK:fast-tests / ring_autotest OK 0.62s
88/112 DPDK:fast-tests / rwlock_test1_autotest OK 1.32s
89/112 DPDK:fast-tests / rwlock_rda_autotest OK 5.58s
90/112 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.58s
91/112 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.58s
92/112 DPDK:fast-tests / sched_autotest OK 0.57s
93/112 DPDK:fast-tests / security_autotest OK 0.12s
94/112 DPDK:fast-tests / seqlock_autotest OK 2.32s
95/112 DPDK:fast-tests / service_autotest OK 3.27s
96/112 DPDK:fast-tests / spinlock_autotest OK 0.62s
97/112 DPDK:fast-tests / stack_autotest OK 0.87s
98/112 DPDK:fast-tests / stack_lf_autotest SKIP 0.07s exit status 77
99/112 DPDK:fast-tests / string_autotest OK 0.42s
100/112 DPDK:fast-tests / table_autotest OK 7.69s
101/112 DPDK:fast-tests / tailq_autotest OK 0.42s
102/112 DPDK:fast-tests / telemetry_data_autotest OK 0.42s
103/112 DPDK:fast-tests / telemetry_json_autotest OK 0.42s
104/112 DPDK:fast-tests / thash_autotest OK 0.42s
105/112 DPDK:fast-tests / threads_autotest OK 0.62s
106/112 DPDK:fast-tests / ticketlock_autotest OK 0.67s
107/112 DPDK:fast-tests / timer_autotest OK 3.92s
108/112 DPDK:fast-tests / trace_autotest OK 0.42s
109/112 DPDK:fast-tests / trace_autotest_with_traces OK 0.42s
110/112 DPDK:fast-tests / vdev_autotest OK 0.42s
111/112 DPDK:fast-tests / version_autotest OK 0.42s
112/112 DPDK:fast-tests / telemetry_all OK 1.32s
Ok: 105
Expected Fail: 0
Fail: 0
Unexpected Pass: 0
Skipped: 7
Timeout: 0
next prev parent reply other threads:[~2024-05-20 4:50 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240520044415.2307157-1-shaiq.wani@intel.com>
2024-05-20 4:17 ` qemudev
2024-05-20 4:22 ` qemudev [this message]
2024-05-20 4:46 ` checkpatch
2024-05-20 5:44 ` 0-day Robot
2024-05-20 6:02 ` |SUCCESS| pw140183 [PATCH] [v1] net/cpfl: get running host ID for CP dpdklab
2024-05-20 6:06 ` dpdklab
2024-05-20 6:07 ` dpdklab
2024-05-20 6:12 ` dpdklab
2024-05-20 6:16 ` dpdklab
2024-05-20 6:27 ` dpdklab
2024-05-20 6:27 ` dpdklab
2024-05-20 6:27 ` dpdklab
2024-05-20 6:28 ` dpdklab
2024-05-20 6:28 ` dpdklab
2024-05-20 6:28 ` dpdklab
2024-05-20 6:28 ` dpdklab
2024-05-20 6:29 ` dpdklab
2024-05-20 6:29 ` dpdklab
2024-05-20 6:29 ` dpdklab
2024-05-20 6:29 ` dpdklab
2024-05-20 6:30 ` dpdklab
2024-05-20 6:30 ` dpdklab
2024-05-20 6:30 ` dpdklab
2024-05-20 6:30 ` dpdklab
2024-05-20 6:30 ` dpdklab
2024-05-20 6:31 ` dpdklab
2024-05-20 6:31 ` dpdklab
2024-05-20 6:32 ` dpdklab
2024-05-20 6:32 ` dpdklab
2024-05-20 6:32 ` dpdklab
2024-05-20 6:32 ` dpdklab
2024-05-20 6:32 ` dpdklab
2024-05-20 6:33 ` dpdklab
2024-05-20 6:35 ` dpdklab
2024-05-20 6:36 ` dpdklab
2024-05-20 6:36 ` dpdklab
2024-05-20 6:37 ` dpdklab
2024-05-20 6:39 ` dpdklab
2024-05-20 6:43 ` dpdklab
2024-05-20 6:44 ` dpdklab
2024-05-20 6:44 ` dpdklab
2024-05-20 6:45 ` dpdklab
2024-05-20 6:45 ` dpdklab
2024-05-20 6:47 ` dpdklab
2024-05-20 6:47 ` dpdklab
2024-05-20 6:48 ` dpdklab
2024-05-20 6:51 ` dpdklab
2024-05-20 6:52 ` dpdklab
2024-05-20 6:52 ` dpdklab
2024-05-20 6:53 ` dpdklab
2024-05-20 6:54 ` dpdklab
2024-05-20 6:54 ` dpdklab
2024-05-20 6:54 ` dpdklab
2024-05-20 6:55 ` dpdklab
2024-05-20 6:56 ` dpdklab
2024-05-20 6:57 ` dpdklab
2024-05-20 6:57 ` dpdklab
2024-05-20 6:58 ` dpdklab
2024-05-20 7:00 ` dpdklab
2024-05-20 7:00 ` dpdklab
2024-05-20 7:02 ` dpdklab
2024-05-20 7:06 ` dpdklab
2024-05-20 7:08 ` dpdklab
2024-05-20 7:08 ` dpdklab
2024-05-20 7:09 ` dpdklab
2024-05-20 7:09 ` dpdklab
2024-05-20 7:10 ` dpdklab
2024-05-20 7:10 ` dpdklab
2024-05-20 7:11 ` dpdklab
2024-05-20 7:13 ` dpdklab
2024-05-20 7:14 ` dpdklab
2024-05-20 7:14 ` dpdklab
2024-05-20 7:16 ` dpdklab
2024-05-20 7:17 ` dpdklab
2024-05-20 7:20 ` dpdklab
2024-05-20 7:21 ` dpdklab
2024-05-20 7:22 ` dpdklab
2024-05-20 7:26 ` dpdklab
2024-05-20 7:26 ` dpdklab
2024-05-20 7:30 ` dpdklab
2024-05-20 7:34 ` dpdklab
2024-05-20 7:37 ` dpdklab
2024-05-20 7:53 ` dpdklab
2024-05-20 8:58 ` dpdklab
2024-05-20 9:10 ` dpdklab
2024-05-20 9:18 ` dpdklab
2024-05-20 9:34 ` dpdklab
2024-05-23 6:16 ` 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=202405200422.44K4MC10120723@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).