From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw145988 [PATCH v7] examples/ptpclient: add frequency adjustment
Date: Tue, 15 Oct 2024 16:23:25 +0800 [thread overview]
Message-ID: <202410150823.49F8NPDQ3899955@localhost.localdomain> (raw)
In-Reply-To: <20241015082201.1554637-1-mingjinx.ye@intel.com>
Test-Label: loongarch-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/145988
_Unit Testing PASS_
Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Tue, 15 Oct 2024 08:22:01 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 19d463aacd5a5345365075db65deb8e9b3003654
145988 --> 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/115 DPDK:fast-tests / acl_autotest OK 3.29s
2/115 DPDK:fast-tests / alarm_autotest OK 1.54s
3/115 DPDK:fast-tests / argparse_autotest OK 0.53s
4/115 DPDK:fast-tests / atomic_autotest OK 7.26s
5/115 DPDK:fast-tests / bitcount_autotest OK 0.44s
6/115 DPDK:fast-tests / bitmap_autotest OK 0.44s
7/115 DPDK:fast-tests / bitops_autotest OK 1.94s
8/115 DPDK:fast-tests / bitratestats_autotest OK 0.44s
9/115 DPDK:fast-tests / bitset_autotest OK 3.14s
10/115 DPDK:fast-tests / bpf_autotest OK 0.44s
11/115 DPDK:fast-tests / bpf_convert_autotest OK 0.45s
12/115 DPDK:fast-tests / byteorder_autotest OK 0.44s
13/115 DPDK:fast-tests / cksum_autotest OK 0.44s
14/115 DPDK:fast-tests / cmdline_autotest OK 0.44s
15/115 DPDK:fast-tests / common_autotest OK 1.28s
16/115 DPDK:fast-tests / compressdev_autotest SKIP 0.08s exit status 77
17/115 DPDK:fast-tests / cpuflags_autotest OK 0.43s
18/115 DPDK:fast-tests / crc_autotest OK 0.44s
19/115 DPDK:fast-tests / user_delay_us OK 0.44s
20/115 DPDK:fast-tests / debug_autotest OK 22.06s
21/115 DPDK:fast-tests / devargs_autotest OK 0.43s
22/115 DPDK:fast-tests / dispatcher_autotest OK 2.60s
23/115 DPDK:fast-tests / distributor_autotest OK 1.23s
24/115 DPDK:fast-tests / eal_flags_c_opt_autotest OK 1.15s
25/115 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.30s
26/115 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.26s
27/115 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.16s
28/115 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.29s
29/115 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.41s
30/115 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.33s
31/115 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.25s
32/115 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.25s
33/115 DPDK:fast-tests / eal_flags_mem_autotest OK 0.71s
34/115 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 22.39s
35/115 DPDK:fast-tests / eal_flags_misc_autotest OK 1.11s
36/115 DPDK:fast-tests / eal_fs_autotest OK 0.44s
37/115 DPDK:fast-tests / errno_autotest OK 0.44s
38/115 DPDK:fast-tests / ethdev_link_status OK 0.44s
39/115 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.72s
40/115 DPDK:fast-tests / event_ring_autotest OK 0.44s
41/115 DPDK:fast-tests / eventdev_common_autotest OK 0.44s
42/115 DPDK:fast-tests / eventdev_selftest_sw OK 7.44s
43/115 DPDK:fast-tests / fbarray_autotest OK 0.44s
44/115 DPDK:fast-tests / fib_autotest OK 1.30s
45/115 DPDK:fast-tests / fib6_autotest OK 1.13s
46/115 DPDK:fast-tests / func_reentrancy_autotest OK 2.29s
47/115 DPDK:fast-tests / graph_autotest OK 0.45s
48/115 DPDK:fast-tests / node_list_dump OK 0.44s
49/115 DPDK:fast-tests / hash_autotest OK 1.25s
50/115 DPDK:fast-tests / hash_readwrite_func_autotest OK 6.46s
51/115 DPDK:fast-tests / interrupt_autotest OK 1.74s
52/115 DPDK:fast-tests / ipfrag_autotest OK 0.09s
53/115 DPDK:fast-tests / ipsec_autotest SKIP 0.44s exit status 77
54/115 DPDK:fast-tests / kvargs_autotest OK 0.44s
55/115 DPDK:fast-tests / latencystats_autotest OK 0.45s
56/115 DPDK:fast-tests / lcores_autotest OK 5.25s
57/115 DPDK:fast-tests / logs_autotest OK 0.44s
58/115 DPDK:fast-tests / lpm_autotest OK 2.49s
59/115 DPDK:fast-tests / lpm6_autotest OK 5.59s
60/115 DPDK:fast-tests / malloc_autotest OK 62.08s
61/115 DPDK:fast-tests / mbuf_autotest OK 4.51s
62/115 DPDK:fast-tests / mcslock_autotest OK 3.83s
63/115 DPDK:fast-tests / member_autotest OK 1.64s
64/115 DPDK:fast-tests / memcpy_autotest OK 7.04s
65/115 DPDK:fast-tests / memory_autotest OK 0.11s
66/115 DPDK:fast-tests / mempool_autotest OK 0.44s
67/115 DPDK:fast-tests / memzone_autotest OK 0.15s
68/115 DPDK:fast-tests / meter_autotest OK 0.44s
69/115 DPDK:fast-tests / metrics_autotest OK 0.44s
70/115 DPDK:fast-tests / multiprocess_autotest OK 0.24s
71/115 DPDK:fast-tests / net_ether_autotest OK 1.10s
72/115 DPDK:fast-tests / pcapng_autotest OK 6.96s
73/115 DPDK:fast-tests / pdcp_autotest SKIP 0.08s exit status 77
74/115 DPDK:fast-tests / pdump_autotest OK 0.56s
75/115 DPDK:fast-tests / per_lcore_autotest OK 0.54s
76/115 DPDK:fast-tests / pflock_autotest OK 1.27s
77/115 DPDK:fast-tests / pie_autotest OK 0.44s
78/115 DPDK:fast-tests / ring_pmd_autotest OK 0.44s
79/115 DPDK:fast-tests / power_autotest OK 0.44s
80/115 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.08s exit status 77
81/115 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.44s exit status 77
82/115 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.08s exit status 77
83/115 DPDK:fast-tests / prefetch_autotest OK 0.44s
84/115 DPDK:fast-tests / ptr_compress_autotest OK 0.44s
85/115 DPDK:fast-tests / rawdev_autotest OK 0.44s
86/115 DPDK:fast-tests / rcu_qsbr_autotest OK 0.96s
87/115 DPDK:fast-tests / reorder_autotest OK 0.50s
88/115 DPDK:fast-tests / rib_autotest OK 9.12s
89/115 DPDK:fast-tests / rib6_autotest OK 9.10s
90/115 DPDK:fast-tests / ring_autotest OK 0.47s
91/115 DPDK:fast-tests / rwlock_test1_autotest OK 1.22s
92/115 DPDK:fast-tests / rwlock_rda_autotest OK 5.44s
93/115 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.44s
94/115 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.44s
95/115 DPDK:fast-tests / sched_autotest OK 0.44s
96/115 DPDK:fast-tests / security_autotest OK 0.08s
97/115 DPDK:fast-tests / seqlock_autotest OK 2.44s
98/115 DPDK:fast-tests / service_autotest OK 3.16s
99/115 DPDK:fast-tests / spinlock_autotest OK 0.52s
100/115 DPDK:fast-tests / stack_autotest OK 0.88s
101/115 DPDK:fast-tests / stack_lf_autotest SKIP 0.07s exit status 77
102/115 DPDK:fast-tests / string_autotest OK 0.44s
103/115 DPDK:fast-tests / table_autotest OK 7.91s
104/115 DPDK:fast-tests / tailq_autotest OK 0.43s
105/115 DPDK:fast-tests / telemetry_data_autotest OK 0.45s
106/115 DPDK:fast-tests / telemetry_json_autotest OK 0.44s
107/115 DPDK:fast-tests / thash_autotest OK 0.45s
108/115 DPDK:fast-tests / threads_autotest OK 0.61s
109/115 DPDK:fast-tests / ticketlock_autotest OK 0.62s
110/115 DPDK:fast-tests / timer_autotest OK 3.97s
111/115 DPDK:fast-tests / trace_autotest OK 0.44s
112/115 DPDK:fast-tests / trace_autotest_with_traces OK 0.45s
113/115 DPDK:fast-tests / vdev_autotest OK 0.44s
114/115 DPDK:fast-tests / version_autotest OK 0.44s
115/115 DPDK:fast-tests / telemetry_all OK 1.40s
Ok: 108
Expected Fail: 0
Fail: 0
Unexpected Pass: 0
Skipped: 7
Timeout: 0
next prev parent reply other threads:[~2024-10-15 8:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241015082201.1554637-1-mingjinx.ye@intel.com>
2024-10-15 8:18 ` qemudev
2024-10-15 8:23 ` qemudev [this message]
2024-10-15 8:46 ` |WARNING| " checkpatch
2024-10-15 9:44 ` |FAILURE| " 0-day Robot
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=202410150823.49F8NPDQ3899955@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).