From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw148914-148921 [PATCH v5 8/8] devtools: add script to generate DPDK dependency graphs
Date: Wed, 27 Nov 2024 22:33:26 +0800 [thread overview]
Message-ID: <202411271433.4AREXQk91143172@localhost.localdomain> (raw)
In-Reply-To: <904bd8ee5aa3e6e2a6444b625329dd3d5438761a.1732719309.git.anatoly.burakov@intel.com>
Test-Label: loongarch-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/148921
_Unit Testing PASS_
Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Wed, 27 Nov 2024 14:56:49 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 4843aacb0d1201fef37e8a579fcd8baec4acdf98
148914-148921 --> 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/118 DPDK:fast-tests / acl_autotest OK 3.42s
2/118 DPDK:fast-tests / alarm_autotest OK 1.61s
3/118 DPDK:fast-tests / argparse_autotest OK 0.60s
4/118 DPDK:fast-tests / atomic_autotest OK 7.08s
5/118 DPDK:fast-tests / bitcount_autotest OK 0.43s
6/118 DPDK:fast-tests / bitmap_autotest OK 0.54s
7/118 DPDK:fast-tests / bitops_autotest OK 2.02s
8/118 DPDK:fast-tests / bitratestats_autotest OK 0.55s
9/118 DPDK:fast-tests / bitset_autotest OK 3.12s
10/118 DPDK:fast-tests / bpf_autotest OK 0.53s
11/118 DPDK:fast-tests / bpf_convert_autotest OK 0.54s
12/118 DPDK:fast-tests / byteorder_autotest OK 0.53s
13/118 DPDK:fast-tests / cfgfile_autotest OK 0.54s
14/118 DPDK:fast-tests / cksum_autotest OK 0.53s
15/118 DPDK:fast-tests / cmdline_autotest OK 0.53s
16/118 DPDK:fast-tests / common_autotest OK 1.42s
17/118 DPDK:fast-tests / compressdev_autotest SKIP 0.06s exit status 77
18/118 DPDK:fast-tests / cpuflags_autotest OK 0.31s
19/118 DPDK:fast-tests / crc_autotest OK 0.31s
20/118 DPDK:fast-tests / user_delay_us OK 0.31s
21/118 DPDK:fast-tests / debug_autotest OK 18.02s
22/118 DPDK:fast-tests / devargs_autotest OK 0.31s
23/118 DPDK:fast-tests / dispatcher_autotest OK 2.52s
24/118 DPDK:fast-tests / distributor_autotest OK 1.20s
25/118 DPDK:fast-tests / eal_flags_c_opt_autotest OK 0.81s
26/118 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.23s
27/118 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.20s
28/118 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.13s
29/118 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.23s
30/118 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.31s
31/118 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.25s
32/118 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.20s
33/118 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.19s
34/118 DPDK:fast-tests / eal_flags_mem_autotest OK 0.61s
35/118 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 22.35s
36/118 DPDK:fast-tests / eal_flags_misc_autotest OK 1.09s
37/118 DPDK:fast-tests / eal_fs_autotest OK 0.31s
38/118 DPDK:fast-tests / errno_autotest OK 0.31s
39/118 DPDK:fast-tests / ethdev_link_status OK 0.31s
40/118 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.68s
41/118 DPDK:fast-tests / event_ring_autotest OK 0.31s
42/118 DPDK:fast-tests / eventdev_common_autotest OK 0.31s
43/118 DPDK:fast-tests / eventdev_selftest_sw OK 7.41s
44/118 DPDK:fast-tests / fbarray_autotest OK 0.31s
45/118 DPDK:fast-tests / fib_autotest OK 1.19s
46/118 DPDK:fast-tests / fib6_autotest OK 0.98s
47/118 DPDK:fast-tests / func_reentrancy_autotest OK 2.36s
48/118 DPDK:fast-tests / graph_autotest OK 0.31s
49/118 DPDK:fast-tests / node_list_dump OK 0.31s
50/118 DPDK:fast-tests / hash_autotest OK 0.94s
51/118 DPDK:fast-tests / hash_readwrite_func_autotest OK 6.41s
52/118 DPDK:fast-tests / interrupt_autotest OK 1.51s
53/118 DPDK:fast-tests / ipfrag_autotest OK 0.07s
54/118 DPDK:fast-tests / ipsec_autotest SKIP 0.31s exit status 77
55/118 DPDK:fast-tests / kvargs_autotest OK 0.31s
56/118 DPDK:fast-tests / latencystats_autotest OK 0.32s
57/118 DPDK:fast-tests / lcore_var_autotest OK 0.46s
58/118 DPDK:fast-tests / lcores_autotest OK 5.12s
59/118 DPDK:fast-tests / logs_autotest OK 0.31s
60/118 DPDK:fast-tests / lpm_autotest OK 2.37s
61/118 DPDK:fast-tests / lpm6_autotest OK 5.45s
62/118 DPDK:fast-tests / malloc_autotest OK 63.52s
63/118 DPDK:fast-tests / mbuf_autotest OK 4.96s
64/118 DPDK:fast-tests / mcslock_autotest OK 2.98s
65/118 DPDK:fast-tests / member_autotest OK 1.51s
66/118 DPDK:fast-tests / memcpy_autotest OK 6.59s
67/118 DPDK:fast-tests / memory_autotest OK 0.08s
68/118 DPDK:fast-tests / mempool_autotest OK 0.43s
69/118 DPDK:fast-tests / memzone_autotest OK 0.14s
70/118 DPDK:fast-tests / meter_autotest OK 0.31s
71/118 DPDK:fast-tests / metrics_autotest OK 0.31s
72/118 DPDK:fast-tests / multiprocess_autotest OK 0.18s
73/118 DPDK:fast-tests / net_ether_autotest OK 0.97s
74/118 DPDK:fast-tests / net_ipv6_autotest OK 0.31s
75/118 DPDK:fast-tests / pcapng_autotest OK 6.10s
76/118 DPDK:fast-tests / pdcp_autotest SKIP 0.06s exit status 77
77/118 DPDK:fast-tests / pdump_autotest OK 0.42s
78/118 DPDK:fast-tests / per_lcore_autotest OK 0.41s
79/118 DPDK:fast-tests / pflock_autotest OK 1.12s
80/118 DPDK:fast-tests / pie_autotest OK 0.31s
81/118 DPDK:fast-tests / ring_pmd_autotest OK 0.31s
82/118 DPDK:fast-tests / power_autotest OK 0.31s
83/118 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.06s exit status 77
84/118 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.31s exit status 77
85/118 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.06s exit status 77
86/118 DPDK:fast-tests / prefetch_autotest OK 0.31s
87/118 DPDK:fast-tests / ptr_compress_autotest OK 0.31s
88/118 DPDK:fast-tests / rawdev_autotest OK 0.31s
89/118 DPDK:fast-tests / rcu_qsbr_autotest OK 0.83s
90/118 DPDK:fast-tests / reorder_autotest OK 0.37s
91/118 DPDK:fast-tests / rib_autotest OK 8.94s
92/118 DPDK:fast-tests / rib6_autotest OK 8.91s
93/118 DPDK:fast-tests / ring_autotest OK 0.34s
94/118 DPDK:fast-tests / rwlock_test1_autotest OK 1.06s
95/118 DPDK:fast-tests / rwlock_rda_autotest OK 5.31s
96/118 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.31s
97/118 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.31s
98/118 DPDK:fast-tests / sched_autotest OK 0.31s
99/118 DPDK:fast-tests / security_autotest OK 0.06s
100/118 DPDK:fast-tests / seqlock_autotest OK 2.31s
101/118 DPDK:fast-tests / service_autotest OK 3.01s
102/118 DPDK:fast-tests / spinlock_autotest OK 0.56s
103/118 DPDK:fast-tests / stack_autotest OK 0.86s
104/118 DPDK:fast-tests / stack_lf_autotest SKIP 0.05s exit status 77
105/118 DPDK:fast-tests / string_autotest OK 0.31s
106/118 DPDK:fast-tests / table_autotest OK 7.51s
107/118 DPDK:fast-tests / tailq_autotest OK 0.30s
108/118 DPDK:fast-tests / telemetry_data_autotest OK 0.31s
109/118 DPDK:fast-tests / telemetry_json_autotest OK 0.31s
110/118 DPDK:fast-tests / thash_autotest OK 0.32s
111/118 DPDK:fast-tests / threads_autotest OK 0.49s
112/118 DPDK:fast-tests / ticketlock_autotest OK 0.46s
113/118 DPDK:fast-tests / timer_autotest OK 3.87s
114/118 DPDK:fast-tests / trace_autotest OK 0.31s
115/118 DPDK:fast-tests / trace_autotest_with_traces OK 0.31s
116/118 DPDK:fast-tests / vdev_autotest OK 0.31s
117/118 DPDK:fast-tests / version_autotest OK 0.31s
118/118 DPDK:fast-tests / telemetry_all OK 1.27s
Ok: 111
Expected Fail: 0
Fail: 0
Unexpected Pass: 0
Skipped: 7
Timeout: 0
next prev parent reply other threads:[~2024-11-29 18:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <904bd8ee5aa3e6e2a6444b625329dd3d5438761a.1732719309.git.anatoly.burakov@intel.com>
2024-11-27 14:28 ` qemudev
2024-11-27 14:33 ` qemudev [this message]
2024-11-27 14:59 ` |SUCCESS| pw148921 " checkpatch
2024-11-27 15:27 ` |FAILURE| pw148914-148921 [PATCH] [v5, " dpdklab
2024-11-27 15:43 ` |FAILURE| pw148921 [PATCH v5 " 0-day Robot
2024-11-29 8:04 ` |SUCCESS| pw148914-148921 " qemudev
2024-11-29 8:05 ` qemudev
2024-11-29 10:21 ` qemudev
2024-11-29 10:21 ` qemudev
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=202411271433.4AREXQk91143172@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).