From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw129211 [PATCH] fib: fix adding a default route
Date: Mon, 3 Jul 2023 23:35:15 +0800 [thread overview]
Message-ID: <202307031535.363FZFkT4016643@localhost.localdomain> (raw)
In-Reply-To: <20230703154335.69883-1-vladimir.medvedkin@intel.com>
Test-Label: loongarch-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/129211
_Unit Testing PASS_
Submitter: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Date: Mon, 3 Jul 2023 15:43:35 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 5afed6966da072e7f569871d86421e70c2326601
129211 --> 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/107 DPDK:fast-tests / acl_autotest OK 2.77s
2/107 DPDK:fast-tests / atomic_autotest OK 6.98s
3/107 DPDK:fast-tests / bitmap_autotest OK 0.07s
4/107 DPDK:fast-tests / bpf_autotest OK 0.07s
5/107 DPDK:fast-tests / bpf_convert_autotest OK 0.07s
6/107 DPDK:fast-tests / bitops_autotest OK 0.07s
7/107 DPDK:fast-tests / byteorder_autotest OK 0.07s
8/107 DPDK:fast-tests / cksum_autotest OK 0.07s
9/107 DPDK:fast-tests / cmdline_autotest OK 0.07s
10/107 DPDK:fast-tests / common_autotest OK 0.92s
11/107 DPDK:fast-tests / cpuflags_autotest OK 0.07s
12/107 DPDK:fast-tests / debug_autotest OK 0.67s
13/107 DPDK:fast-tests / devargs_autotest OK 0.07s
14/107 DPDK:fast-tests / eal_flags_c_opt_autotest OK 1.07s
15/107 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.27s
16/107 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.27s
17/107 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.17s
18/107 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.27s
19/107 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.37s
20/107 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.32s
21/107 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.22s
22/107 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.22s
23/107 DPDK:fast-tests / eal_flags_mem_autotest OK 0.67s
24/107 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 22.31s
25/107 DPDK:fast-tests / eal_flags_misc_autotest OK 1.02s
26/107 DPDK:fast-tests / eal_fs_autotest OK 0.07s
27/107 DPDK:fast-tests / errno_autotest OK 0.07s
28/107 DPDK:fast-tests / ethdev_link_status OK 0.07s
29/107 DPDK:fast-tests / event_ring_autotest OK 0.07s
30/107 DPDK:fast-tests / fib_autotest OK 0.87s
31/107 DPDK:fast-tests / fib6_autotest OK 0.92s
32/107 DPDK:fast-tests / func_reentrancy_autotest OK 2.18s
33/107 DPDK:fast-tests / hash_autotest OK 1.02s
34/107 DPDK:fast-tests / interrupt_autotest OK 1.37s
35/107 DPDK:fast-tests / ipfrag_autotest OK 0.07s
36/107 DPDK:fast-tests / lcores_autotest OK 5.12s
37/107 DPDK:fast-tests / logs_autotest OK 0.07s
38/107 DPDK:fast-tests / lpm_autotest OK 5.95s
39/107 DPDK:fast-tests / lpm6_autotest OK 8.91s
40/107 DPDK:fast-tests / malloc_autotest OK 60.55s
41/107 DPDK:fast-tests / mbuf_autotest OK 5.07s
42/107 DPDK:fast-tests / mcslock_autotest OK 2.57s
43/107 DPDK:fast-tests / memcpy_autotest OK 6.68s
44/107 DPDK:fast-tests / memory_autotest OK 0.12s
45/107 DPDK:fast-tests / mempool_autotest OK 0.47s
46/107 DPDK:fast-tests / memzone_autotest OK 0.17s
47/107 DPDK:fast-tests / meter_autotest OK 0.07s
48/107 DPDK:fast-tests / multiprocess_autotest OK 0.22s
49/107 DPDK:fast-tests / per_lcore_autotest OK 0.17s
50/107 DPDK:fast-tests / pflock_autotest OK 0.92s
51/107 DPDK:fast-tests / prefetch_autotest OK 0.07s
52/107 DPDK:fast-tests / rcu_qsbr_autotest OK 0.62s
53/107 DPDK:fast-tests / pie_autotest OK 0.07s
54/107 DPDK:fast-tests / rib_autotest OK 10.29s
55/107 DPDK:fast-tests / rib6_autotest OK 10.34s
56/107 DPDK:fast-tests / ring_autotest OK 0.12s
57/107 DPDK:fast-tests / rwlock_test1_autotest OK 0.87s
58/107 DPDK:fast-tests / rwlock_rda_autotest OK 5.07s
59/107 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.07s
60/107 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.07s
61/107 DPDK:fast-tests / sched_autotest OK 0.07s
62/107 DPDK:fast-tests / security_autotest OK 0.07s
63/107 DPDK:fast-tests / seqlock_autotest OK 2.07s
64/107 DPDK:fast-tests / spinlock_autotest OK 0.17s
65/107 DPDK:fast-tests / stack_autotest OK 0.87s
66/107 DPDK:fast-tests / stack_lf_autotest SKIP 0.07s exit status 77
67/107 DPDK:fast-tests / string_autotest OK 0.07s
68/107 DPDK:fast-tests / tailq_autotest OK 0.07s
69/107 DPDK:fast-tests / ticketlock_autotest OK 0.22s
70/107 DPDK:fast-tests / timer_autotest OK 3.92s
71/107 DPDK:fast-tests / user_delay_us OK 0.07s
72/107 DPDK:fast-tests / version_autotest OK 0.07s
73/107 DPDK:fast-tests / crc_autotest OK 0.07s
74/107 DPDK:fast-tests / distributor_autotest OK 1.22s
75/107 DPDK:fast-tests / eventdev_common_autotest OK 0.07s
76/107 DPDK:fast-tests / fbarray_autotest OK 0.07s
77/107 DPDK:fast-tests / hash_readwrite_func_autotest OK 6.43s
78/107 DPDK:fast-tests / ipsec_autotest SKIP 0.07s exit status 77
79/107 DPDK:fast-tests / kni_autotest SKIP 0.07s exit status 77
80/107 DPDK:fast-tests / kvargs_autotest OK 0.07s
81/107 DPDK:fast-tests / member_autotest OK 1.27s
82/107 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.07s exit status 77
83/107 DPDK:fast-tests / power_autotest OK 0.07s
84/107 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.07s exit status 77
85/107 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.07s exit status 77
86/107 DPDK:fast-tests / reorder_autotest OK 0.12s
87/107 DPDK:fast-tests / service_autotest OK 2.82s
88/107 DPDK:fast-tests / thash_autotest OK 0.07s
89/107 DPDK:fast-tests / threads_autotest OK 0.27s
90/107 DPDK:fast-tests / trace_autotest OK 0.07s
91/107 DPDK:fast-tests / trace_autotest_with_traces OK 0.12s
92/107 DPDK:fast-tests / graph_autotest OK 0.07s
93/107 DPDK:fast-tests / node_list_dump OK 0.07s
94/107 DPDK:fast-tests / metrics_autotest OK 0.07s
95/107 DPDK:fast-tests / telemetry_json_autotest OK 0.07s
96/107 DPDK:fast-tests / telemetry_data_autotest OK 0.07s
97/107 DPDK:fast-tests / table_autotest OK 10.15s
98/107 DPDK:fast-tests / ring_pmd_autotest OK 0.07s
99/107 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.72s
100/107 DPDK:fast-tests / bitratestats_autotest OK 0.07s
101/107 DPDK:fast-tests / latencystats_autotest OK 0.07s
102/107 DPDK:fast-tests / pdump_autotest OK 5.17s
103/107 DPDK:fast-tests / vdev_autotest OK 0.07s
104/107 DPDK:fast-tests / rawdev_autotest OK 0.07s
105/107 DPDK:fast-tests / pdcp_autotest SKIP 0.07s exit status 77
106/107 DPDK:fast-tests / compressdev_autotest SKIP 0.07s exit status 77
107/107 DPDK:fast-tests / telemetry_all OK 17.30s
Ok: 99
Expected Fail: 0
Fail: 0
Unexpected Pass: 0
Skipped: 8
Timeout: 0
next prev parent reply other threads:[~2023-07-03 15:49 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230703154335.69883-1-vladimir.medvedkin@intel.com>
2023-07-03 15:31 ` qemudev
2023-07-03 15:35 ` qemudev [this message]
2023-07-03 15:44 ` checkpatch
2023-07-03 16:39 ` 0-day Robot
2023-07-06 3:38 dpdklab
2023-07-06 3:40 dpdklab
2023-07-06 4:02 dpdklab
2023-07-06 4:38 dpdklab
2023-07-06 4:38 dpdklab
2023-07-06 4:38 dpdklab
2023-07-06 4:44 dpdklab
2023-07-06 4:45 dpdklab
2023-07-06 4:48 dpdklab
2023-07-06 4:49 dpdklab
2023-07-06 4:57 dpdklab
2023-07-06 4:57 dpdklab
2023-07-06 5:04 dpdklab
2023-07-06 5:06 dpdklab
2023-07-06 9:34 dpdklab
2023-07-06 9:50 dpdklab
2023-07-06 12:06 dpdklab
2023-07-06 21:17 dpdklab
2023-07-08 6:58 dpdklab
2023-07-08 7:17 dpdklab
2023-07-10 21:42 dpdklab
2023-07-10 22:38 dpdklab
2023-07-11 22:02 dpdklab
2023-07-11 22:36 dpdklab
2023-07-11 23:06 dpdklab
2023-07-11 23:09 dpdklab
2023-07-12 0:20 dpdklab
2023-07-12 5:46 dpdklab
2023-07-12 5:51 dpdklab
2023-07-12 7:19 dpdklab
2023-07-12 21:20 dpdklab
2023-07-14 19:45 dpdklab
2023-07-14 19:45 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=202307031535.363FZFkT4016643@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).