From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw133867 [PATCH] net/bnxt: fix deadlock in mgr timer cb
Date: Sat, 4 Nov 2023 12:03:52 +0800 [thread overview]
Message-ID: <202311040403.3A443qmr4162661@localhost.localdomain> (raw)
In-Reply-To: <tencent_7B6D2301220A31DB3CA9A701112E3A47DF08@qq.com>
Test-Label: loongarch-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/133867
_Unit Testing PASS_
Submitter: Weiguo Li <liwg06@foxmail.com>
Date: Sat, 4 Nov 2023 12:06:58 +0800
DPDK git baseline: Repo:dpdk-next-net-brcm
Branch: for-next-net
CommitID: ecca8a0be606f4bbdeee1e76bdce16c3e1ff4d89
133867 --> 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/110 DPDK:fast-tests / acl_autotest OK 3.13s
2/110 DPDK:fast-tests / atomic_autotest OK 6.98s
3/110 DPDK:fast-tests / bitcount_autotest OK 0.22s
4/110 DPDK:fast-tests / bitmap_autotest OK 0.22s
5/110 DPDK:fast-tests / bitops_autotest OK 0.22s
6/110 DPDK:fast-tests / bitratestats_autotest OK 0.22s
7/110 DPDK:fast-tests / bpf_autotest OK 0.22s
8/110 DPDK:fast-tests / bpf_convert_autotest OK 0.22s
9/110 DPDK:fast-tests / byteorder_autotest OK 0.22s
10/110 DPDK:fast-tests / cksum_autotest OK 0.22s
11/110 DPDK:fast-tests / cmdline_autotest OK 0.22s
12/110 DPDK:fast-tests / common_autotest OK 1.07s
13/110 DPDK:fast-tests / compressdev_autotest SKIP 0.07s exit status 77
14/110 DPDK:fast-tests / cpuflags_autotest OK 0.22s
15/110 DPDK:fast-tests / crc_autotest OK 0.22s
16/110 DPDK:fast-tests / user_delay_us OK 0.22s
17/110 DPDK:fast-tests / debug_autotest OK 12.45s
18/110 DPDK:fast-tests / devargs_autotest OK 0.37s
19/110 DPDK:fast-tests / dispatcher_autotest OK 2.47s
20/110 DPDK:fast-tests / distributor_autotest OK 1.27s
21/110 DPDK:fast-tests / eal_flags_c_opt_autotest OK 1.17s
22/110 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.32s
23/110 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.27s
24/110 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.17s
25/110 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.32s
26/110 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.42s
27/110 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.37s
28/110 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.27s
29/110 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.27s
30/110 DPDK:fast-tests / eal_flags_mem_autotest OK 0.72s
31/110 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 22.36s
32/110 DPDK:fast-tests / eal_flags_misc_autotest OK 1.12s
33/110 DPDK:fast-tests / eal_fs_autotest OK 0.32s
34/110 DPDK:fast-tests / errno_autotest OK 0.32s
35/110 DPDK:fast-tests / ethdev_link_status OK 0.32s
36/110 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.72s
37/110 DPDK:fast-tests / event_ring_autotest OK 0.32s
38/110 DPDK:fast-tests / eventdev_common_autotest OK 0.32s
39/110 DPDK:fast-tests / eventdev_selftest_sw OK 7.23s
40/110 DPDK:fast-tests / fbarray_autotest OK 0.32s
41/110 DPDK:fast-tests / fib_autotest OK 1.02s
42/110 DPDK:fast-tests / fib6_autotest OK 1.07s
43/110 DPDK:fast-tests / func_reentrancy_autotest OK 2.18s
44/110 DPDK:fast-tests / graph_autotest OK 0.32s
45/110 DPDK:fast-tests / node_list_dump OK 0.32s
46/110 DPDK:fast-tests / hash_autotest OK 1.27s
47/110 DPDK:fast-tests / hash_readwrite_func_autotest OK 6.43s
48/110 DPDK:fast-tests / interrupt_autotest OK 1.62s
49/110 DPDK:fast-tests / ipfrag_autotest OK 0.12s
50/110 DPDK:fast-tests / ipsec_autotest SKIP 0.32s exit status 77
51/110 DPDK:fast-tests / kvargs_autotest OK 0.32s
52/110 DPDK:fast-tests / latencystats_autotest OK 0.32s
53/110 DPDK:fast-tests / lcores_autotest OK 5.38s
54/110 DPDK:fast-tests / logs_autotest OK 0.32s
55/110 DPDK:fast-tests / lpm_autotest OK 2.38s
56/110 DPDK:fast-tests / lpm6_autotest OK 5.54s
57/110 DPDK:fast-tests / malloc_autotest OK 62.55s
58/110 DPDK:fast-tests / mbuf_autotest OK 5.12s
59/110 DPDK:fast-tests / mcslock_autotest OK 3.27s
60/110 DPDK:fast-tests / member_autotest OK 1.52s
61/110 DPDK:fast-tests / memcpy_autotest OK 7.23s
62/110 DPDK:fast-tests / memory_autotest OK 0.12s
63/110 DPDK:fast-tests / mempool_autotest OK 0.47s
64/110 DPDK:fast-tests / memzone_autotest OK 0.17s
65/110 DPDK:fast-tests / meter_autotest OK 0.32s
66/110 DPDK:fast-tests / metrics_autotest OK 0.32s
67/110 DPDK:fast-tests / multiprocess_autotest OK 0.27s
68/110 DPDK:fast-tests / net_ether_autotest OK 1.02s
69/110 DPDK:fast-tests / pdcp_autotest SKIP 0.07s exit status 77
70/110 DPDK:fast-tests / pdump_autotest OK 0.47s
71/110 DPDK:fast-tests / per_lcore_autotest OK 0.42s
72/110 DPDK:fast-tests / pflock_autotest OK 1.17s
73/110 DPDK:fast-tests / pie_autotest OK 0.32s
74/110 DPDK:fast-tests / ring_pmd_autotest OK 0.32s
75/110 DPDK:fast-tests / power_autotest OK 0.32s
76/110 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.07s exit status 77
77/110 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.32s exit status 77
78/110 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.07s exit status 77
79/110 DPDK:fast-tests / prefetch_autotest OK 0.32s
80/110 DPDK:fast-tests / rawdev_autotest OK 0.32s
81/110 DPDK:fast-tests / rcu_qsbr_autotest OK 0.87s
82/110 DPDK:fast-tests / reorder_autotest OK 0.37s
83/110 DPDK:fast-tests / rib_autotest OK 8.99s
84/110 DPDK:fast-tests / rib6_autotest OK 8.99s
85/110 DPDK:fast-tests / ring_autotest OK 0.37s
86/110 DPDK:fast-tests / rwlock_test1_autotest OK 1.12s
87/110 DPDK:fast-tests / rwlock_rda_autotest OK 5.33s
88/110 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.33s
89/110 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.33s
90/110 DPDK:fast-tests / sched_autotest OK 0.32s
91/110 DPDK:fast-tests / security_autotest OK 0.07s
92/110 DPDK:fast-tests / seqlock_autotest OK 2.32s
93/110 DPDK:fast-tests / service_autotest OK 3.07s
94/110 DPDK:fast-tests / spinlock_autotest OK 0.42s
95/110 DPDK:fast-tests / stack_autotest OK 0.87s
96/110 DPDK:fast-tests / stack_lf_autotest SKIP 0.07s exit status 77
97/110 DPDK:fast-tests / string_autotest OK 0.32s
98/110 DPDK:fast-tests / table_autotest OK 7.79s
99/110 DPDK:fast-tests / tailq_autotest OK 0.32s
100/110 DPDK:fast-tests / telemetry_data_autotest OK 0.32s
101/110 DPDK:fast-tests / telemetry_json_autotest OK 0.32s
102/110 DPDK:fast-tests / thash_autotest OK 0.32s
103/110 DPDK:fast-tests / threads_autotest OK 0.52s
104/110 DPDK:fast-tests / ticketlock_autotest OK 0.52s
105/110 DPDK:fast-tests / timer_autotest OK 3.92s
106/110 DPDK:fast-tests / trace_autotest OK 0.32s
107/110 DPDK:fast-tests / trace_autotest_with_traces OK 0.32s
108/110 DPDK:fast-tests / vdev_autotest OK 0.32s
109/110 DPDK:fast-tests / version_autotest OK 0.32s
110/110 DPDK:fast-tests / telemetry_all OK 1.27s
Ok: 103
Expected Fail: 0
Fail: 0
Unexpected Pass: 0
Skipped: 7
Timeout: 0
next prev parent reply other threads:[~2023-11-04 4:25 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_7B6D2301220A31DB3CA9A701112E3A47DF08@qq.com>
2023-11-04 3:59 ` qemudev
2023-11-04 4:03 ` qemudev [this message]
2023-11-04 4:07 ` |WARNING| " checkpatch
2023-11-04 5:19 ` |SUCCESS| " 0-day Robot
2023-11-04 5:30 dpdklab
2023-11-04 5:32 dpdklab
2023-11-04 5:32 dpdklab
2023-11-04 5:35 dpdklab
2023-11-04 5:35 dpdklab
2023-11-04 5:36 dpdklab
2023-11-04 5:37 dpdklab
2023-11-04 5:38 dpdklab
2023-11-04 5:38 dpdklab
2023-11-04 5:39 dpdklab
2023-11-04 5:39 dpdklab
2023-11-04 5:40 dpdklab
2023-11-04 5:42 dpdklab
2023-11-04 5:49 dpdklab
2023-11-04 5:49 dpdklab
2023-11-04 5:55 dpdklab
2023-11-04 5:55 dpdklab
2023-11-04 5:55 dpdklab
2023-11-04 5:59 dpdklab
2023-11-04 6:10 dpdklab
2023-11-04 6:29 dpdklab
2023-11-04 7:55 dpdklab
2023-11-04 7:55 dpdklab
2023-11-04 7:55 dpdklab
2023-11-04 7:56 dpdklab
2023-11-04 8:01 dpdklab
2023-11-04 8:17 dpdklab
2023-11-04 8:25 dpdklab
2023-11-04 8:37 dpdklab
2023-11-04 8:47 dpdklab
2023-11-04 8:48 dpdklab
2023-11-04 8:49 dpdklab
2023-11-04 8:50 dpdklab
2023-11-04 8:50 dpdklab
2023-11-04 8:51 dpdklab
2023-11-04 8:51 dpdklab
2023-11-04 8:52 dpdklab
2023-11-04 8:52 dpdklab
2023-11-04 8:52 dpdklab
2023-11-04 8:53 dpdklab
2023-11-04 8:57 dpdklab
2023-11-04 8:58 dpdklab
2023-11-04 9:01 dpdklab
2023-11-04 9:02 dpdklab
2023-11-04 9:02 dpdklab
2023-11-04 9:02 dpdklab
2023-11-04 9:02 dpdklab
2023-11-04 9:03 dpdklab
2023-11-04 9:03 dpdklab
2023-11-04 9:04 dpdklab
2023-11-04 9:07 dpdklab
2023-11-04 9:09 dpdklab
2023-11-04 10:58 dpdklab
2023-11-04 11:01 dpdklab
2023-11-06 15:26 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=202311040403.3A443qmr4162661@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).