* |SUCCESS| pw153182 [PATCH V2] Add new tracepoint function for type time_t
[not found] <20250429030437.1128853-1-changqing.li@windriver.com>
@ 2025-04-29 2:33 ` qemudev
2025-04-29 2:37 ` qemudev
` (2 subsequent siblings)
3 siblings, 0 replies; 4+ messages in thread
From: qemudev @ 2025-04-29 2:33 UTC (permalink / raw)
To: test-report
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/153182
_Compilation OK_
Submitter: Changqing Li <changqing.li@windriver.com>
Date: Tue, 29 Apr 2025 11:04:37 +0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: ca1690ebd224f148268285b15b97441ccdbdd07e
153182 --> meson & ninja build successfully
Test environment and result as below:
+---------------------+----------------+
| Environment | compilation |
+---------------------+----------------+
| Loongnix-Server 8.3 | PASS |
+---------------------+----------------+
Loongnix-Server 8.3
Kernel: 4.19.190+
Compiler: gcc 8.3
^ permalink raw reply [flat|nested] 4+ messages in thread* |SUCCESS| pw153182 [PATCH V2] Add new tracepoint function for type time_t
[not found] <20250429030437.1128853-1-changqing.li@windriver.com>
2025-04-29 2:33 ` |SUCCESS| pw153182 [PATCH V2] Add new tracepoint function for type time_t qemudev
@ 2025-04-29 2:37 ` qemudev
2025-04-29 3:05 ` |WARNING| " checkpatch
2025-04-29 4:23 ` |FAILURE| " 0-day Robot
3 siblings, 0 replies; 4+ messages in thread
From: qemudev @ 2025-04-29 2:37 UTC (permalink / raw)
To: test-report
Test-Label: loongarch-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/153182
_Unit Testing PASS_
Submitter: Changqing Li <changqing.li@windriver.com>
Date: Tue, 29 Apr 2025 11:04:37 +0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: ca1690ebd224f148268285b15b97441ccdbdd07e
153182 --> 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/119 DPDK:fast-tests / acl_autotest OK 3.25s
2/119 DPDK:fast-tests / alarm_autotest OK 1.50s
3/119 DPDK:fast-tests / argparse_autotest OK 0.50s
4/119 DPDK:fast-tests / atomic_autotest OK 6.90s
5/119 DPDK:fast-tests / bitcount_autotest OK 0.48s
6/119 DPDK:fast-tests / bitmap_autotest OK 0.48s
7/119 DPDK:fast-tests / bitops_autotest OK 1.98s
8/119 DPDK:fast-tests / bitratestats_autotest OK 0.48s
9/119 DPDK:fast-tests / bitset_autotest OK 3.25s
10/119 DPDK:fast-tests / bpf_autotest OK 0.48s
11/119 DPDK:fast-tests / bpf_convert_autotest OK 0.49s
12/119 DPDK:fast-tests / byteorder_autotest OK 0.48s
13/119 DPDK:fast-tests / cfgfile_autotest OK 0.48s
14/119 DPDK:fast-tests / cksum_autotest OK 0.48s
15/119 DPDK:fast-tests / cmdline_autotest OK 0.48s
16/119 DPDK:fast-tests / common_autotest OK 1.36s
17/119 DPDK:fast-tests / compressdev_autotest SKIP 0.07s exit status 77
18/119 DPDK:fast-tests / cpuflags_autotest OK 0.47s
19/119 DPDK:fast-tests / crc_autotest OK 0.48s
20/119 DPDK:fast-tests / user_delay_us OK 0.48s
21/119 DPDK:fast-tests / debug_autotest OK 16.51s
22/119 DPDK:fast-tests / devargs_autotest OK 0.48s
23/119 DPDK:fast-tests / dispatcher_autotest OK 2.53s
24/119 DPDK:fast-tests / distributor_autotest OK 1.20s
25/119 DPDK:fast-tests / eal_flags_c_opt_autotest OK 0.80s
26/119 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.23s
27/119 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.20s
28/119 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.14s
29/119 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.23s
30/119 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.31s
31/119 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.26s
32/119 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.20s
33/119 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.19s
34/119 DPDK:fast-tests / eal_flags_mem_autotest OK 0.61s
35/119 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 22.34s
36/119 DPDK:fast-tests / eal_flags_misc_autotest OK 1.10s
37/119 DPDK:fast-tests / eal_fs_autotest OK 0.47s
38/119 DPDK:fast-tests / errno_autotest OK 0.48s
39/119 DPDK:fast-tests / ethdev_link_status OK 0.48s
40/119 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.69s
41/119 DPDK:fast-tests / event_ring_autotest OK 0.48s
42/119 DPDK:fast-tests / eventdev_common_autotest OK 0.48s
43/119 DPDK:fast-tests / eventdev_selftest_sw OK 7.27s
44/119 DPDK:fast-tests / fbarray_autotest OK 0.48s
45/119 DPDK:fast-tests / fib_autotest OK 1.33s
46/119 DPDK:fast-tests / fib6_autotest OK 1.09s
47/119 DPDK:fast-tests / func_reentrancy_autotest OK 2.37s
48/119 DPDK:fast-tests / graph_autotest OK 0.48s
49/119 DPDK:fast-tests / node_list_dump OK 0.48s
50/119 DPDK:fast-tests / hash_autotest OK 1.11s
51/119 DPDK:fast-tests / hash_readwrite_func_autotest OK 6.41s
52/119 DPDK:fast-tests / interrupt_autotest OK 1.78s
53/119 DPDK:fast-tests / ipfrag_autotest OK 0.08s
54/119 DPDK:fast-tests / ipsec_autotest SKIP 0.48s exit status 77
55/119 DPDK:fast-tests / kvargs_autotest OK 0.49s
56/119 DPDK:fast-tests / latencystats_autotest OK 0.49s
57/119 DPDK:fast-tests / lcore_var_autotest OK 0.62s
58/119 DPDK:fast-tests / lcores_autotest OK 5.29s
59/119 DPDK:fast-tests / logs_autotest OK 0.48s
60/119 DPDK:fast-tests / lpm_autotest OK 2.54s
61/119 DPDK:fast-tests / lpm6_autotest OK 5.63s
62/119 DPDK:fast-tests / malloc_autotest OK 62.42s
63/119 DPDK:fast-tests / mbuf_autotest OK 5.17s
64/119 DPDK:fast-tests / mcslock_autotest OK 4.06s
65/119 DPDK:fast-tests / member_autotest OK 1.65s
66/119 DPDK:fast-tests / memcpy_autotest OK 6.92s
67/119 DPDK:fast-tests / memory_autotest OK 0.10s
68/119 DPDK:fast-tests / mempool_autotest OK 0.43s
69/119 DPDK:fast-tests / memzone_autotest OK 0.14s
70/119 DPDK:fast-tests / meter_autotest OK 0.48s
71/119 DPDK:fast-tests / metrics_autotest OK 0.48s
72/119 DPDK:fast-tests / multiprocess_autotest OK 0.20s
73/119 DPDK:fast-tests / net_ether_autotest OK 1.14s
74/119 DPDK:fast-tests / net_ipv6_autotest OK 0.48s
75/119 DPDK:fast-tests / pcapng_autotest OK 6.90s
76/119 DPDK:fast-tests / pdcp_autotest SKIP 0.07s exit status 77
77/119 DPDK:fast-tests / pdump_autotest OK 0.59s
78/119 DPDK:fast-tests / per_lcore_autotest OK 0.58s
79/119 DPDK:fast-tests / pflock_autotest OK 1.29s
80/119 DPDK:fast-tests / pie_autotest OK 0.49s
81/119 DPDK:fast-tests / ring_pmd_autotest OK 0.48s
82/119 DPDK:fast-tests / power_autotest OK 0.48s
83/119 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.07s exit status 77
84/119 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.47s exit status 77
85/119 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.07s exit status 77
86/119 DPDK:fast-tests / prefetch_autotest OK 0.47s
87/119 DPDK:fast-tests / ptr_compress_autotest OK 0.48s
88/119 DPDK:fast-tests / rawdev_autotest OK 0.48s
89/119 DPDK:fast-tests / rcu_qsbr_autotest OK 1.00s
90/119 DPDK:fast-tests / reorder_autotest OK 0.54s
91/119 DPDK:fast-tests / rib_autotest OK 9.14s
92/119 DPDK:fast-tests / rib6_autotest OK 9.13s
93/119 DPDK:fast-tests / ring_autotest OK 0.51s
94/119 DPDK:fast-tests / rwlock_test1_autotest OK 1.23s
95/119 DPDK:fast-tests / rwlock_rda_autotest OK 5.48s
96/119 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.48s
97/119 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.49s
98/119 DPDK:fast-tests / sched_autotest OK 0.48s
99/119 DPDK:fast-tests / security_autotest OK 0.07s
100/119 DPDK:fast-tests / seqlock_autotest OK 2.48s
101/119 DPDK:fast-tests / service_autotest OK 3.18s
102/119 DPDK:fast-tests / soring_autotest OK 0.49s
103/119 DPDK:fast-tests / spinlock_autotest OK 0.56s
104/119 DPDK:fast-tests / stack_autotest OK 0.87s
105/119 DPDK:fast-tests / stack_lf_autotest SKIP 0.06s exit status 77
106/119 DPDK:fast-tests / string_autotest OK 0.48s
107/119 DPDK:fast-tests / table_autotest OK 7.79s
108/119 DPDK:fast-tests / tailq_autotest OK 0.48s
109/119 DPDK:fast-tests / telemetry_data_autotest OK 0.49s
110/119 DPDK:fast-tests / telemetry_json_autotest OK 0.48s
111/119 DPDK:fast-tests / thash_autotest OK 0.49s
112/119 DPDK:fast-tests / threads_autotest OK 0.66s
113/119 DPDK:fast-tests / ticketlock_autotest OK 0.64s
114/119 DPDK:fast-tests / timer_autotest OK 3.97s
115/119 DPDK:fast-tests / trace_autotest OK 0.47s
116/119 DPDK:fast-tests / trace_autotest_with_traces OK 0.49s
117/119 DPDK:fast-tests / vdev_autotest OK 0.47s
118/119 DPDK:fast-tests / version_autotest OK 0.48s
119/119 DPDK:fast-tests / telemetry_all OK 1.40s
Ok: 112
Expected Fail: 0
Fail: 0
Unexpected Pass: 0
Skipped: 7
Timeout: 0
^ permalink raw reply [flat|nested] 4+ messages in thread* |WARNING| pw153182 [PATCH V2] Add new tracepoint function for type time_t
[not found] <20250429030437.1128853-1-changqing.li@windriver.com>
2025-04-29 2:33 ` |SUCCESS| pw153182 [PATCH V2] Add new tracepoint function for type time_t qemudev
2025-04-29 2:37 ` qemudev
@ 2025-04-29 3:05 ` checkpatch
2025-04-29 4:23 ` |FAILURE| " 0-day Robot
3 siblings, 0 replies; 4+ messages in thread
From: checkpatch @ 2025-04-29 3:05 UTC (permalink / raw)
To: test-report; +Cc: changqing.li
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/153182
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#90:
498 | #define RTE_BUILD_BUG_ON(condition) ((void)sizeof(char[1 - 2*!!(condition)]))
total: 0 errors, 1 warnings, 54 lines checked
^ permalink raw reply [flat|nested] 4+ messages in thread* |FAILURE| pw153182 [PATCH V2] Add new tracepoint function for type time_t
[not found] <20250429030437.1128853-1-changqing.li@windriver.com>
` (2 preceding siblings ...)
2025-04-29 3:05 ` |WARNING| " checkpatch
@ 2025-04-29 4:23 ` 0-day Robot
3 siblings, 0 replies; 4+ messages in thread
From: 0-day Robot @ 2025-04-29 4:23 UTC (permalink / raw)
To: test-report; +Cc: changqing.li, robot
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/153182/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/14722692195
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-gcc-abi+debug+doc+examples+tests" failed at step Build and test
"ubuntu-22.04-clang-asan+doc+tests" failed at step Build and test
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################
Full log written to /home/runner/work/dpdk/dpdk/build/meson-logs/testlog.txt
+ catch_coredump
+ ls /tmp/dpdk-core.*.*
+ return 0
+ check_traces
+ which babeltrace
+ sudo find /home/runner -name metadata
+ dirname /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-03-49-48/metadata
+ sudo babeltrace /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-03-49-48
+ dirname /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-03-49-48/metadata
+ sudo babeltrace /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-03-49-48
[error] at line 2819: token "time_t": syntax error, unexpected IDENTIFIER
[error] Error creating AST
[warning] Unable to open trace metadata for path "/home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-03-49-48".
[warning] [Context] Cannot open_trace of format ctf at path /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-03-49-48.
[warning] [Context] cannot open trace "/home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-03-49-48" from /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-03-49-48 for reading.
[error] Cannot open any trace for reading.
[error] opening trace "/home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-03-49-48" for reading.
[error] none of the specified trace paths could be opened.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################
####################################################################################
#### [Begin job log] "ubuntu-22.04-clang-asan+doc+tests" at step Build and test
####################################################################################
Full log written to /home/runner/work/dpdk/dpdk/build/meson-logs/testlog.txt
+ catch_coredump
+ ls /tmp/dpdk-core.*.*
+ return 0
+ check_traces
+ which babeltrace
+ sudo find /home/runner -name metadata
+ dirname /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-04-04-36/metadata
+ sudo babeltrace /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-04-04-36
+ dirname /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-04-04-36/metadata
+ sudo babeltrace /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-04-04-36
[error] at line 2819: token "time_t": syntax error, unexpected IDENTIFIER
[error] Error creating AST
[warning] Unable to open trace metadata for path "/home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-04-04-36".
[warning] [Context] Cannot open_trace of format ctf at path /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-04-04-36.
[warning] [Context] cannot open trace "/home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-04-04-36" from /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-04-04-36 for reading.
[error] Cannot open any trace for reading.
[error] opening trace "/home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-04-04-36" for reading.
[error] none of the specified trace paths could be opened.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-clang-asan+doc+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------
^ permalink raw reply [flat|nested] 4+ messages in thread