From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Tomasz Duszynski <tduszynski@marvell.com>
Subject: |FAILURE| pw150159-150162 [PATCH] [v17,4/4] eal: add PMU support to
Date: Fri, 17 Jan 2025 03:00:08 -0800 (PST) [thread overview]
Message-ID: <678a3838.050a0220.2d6320.7db8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250117090033.2807073-5-tduszynski@marvell.com>
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/150162
_Testing issues_
Submitter: Tomasz Duszynski <tduszynski@marvell.com>
Date: Friday, January 17 2025 09:00:33
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:06e2856620a70000b2a28f0ea715fc247b85fd8d
150159-150162 --> testing issues
Upstream job id: Generic-Unit-Test-DPDK#306732
Test environment and result as below:
+-------------------+----------------+
| Environment | dpdk_unit_test |
+===================+================+
| Debian Bullseye | FAIL |
+-------------------+----------------+
| CentOS Stream 9 | PEND |
+-------------------+----------------+
| Fedora 40 | PEND |
+-------------------+----------------+
| RHEL9 | PEND |
+-------------------+----------------+
| Fedora 40 (Clang) | PEND |
+-------------------+----------------+
| Fedora 41 | PEND |
+-------------------+----------------+
| RHEL8 | PEND |
+-------------------+----------------+
| Debian 12 | PEND |
+-------------------+----------------+
| Fedora 41 (Clang) | PEND |
+-------------------+----------------+
| Ubuntu 22.04 | PEND |
+-------------------+----------------+
| Ubuntu 24.04 | PEND |
+-------------------+----------------+
| Ubuntu 20.04 | PEND |
+-------------------+----------------+
==== Unit test summary for Debian Bullseye (dpdk_unit_test): ====
ninja: Entering directory `/root/workspace/Generic-Unit-Test-DPDK/dpdk/build'
ninja: no work to do.
1/120 DPDK:fast-tests / acl_autotest OK 2.34s
2/120 DPDK:fast-tests / alarm_autotest OK 1.17s
3/120 DPDK:fast-tests / argparse_autotest OK 0.17s
4/120 DPDK:fast-tests / atomic_autotest OK 0.34s
5/120 DPDK:fast-tests / bitcount_autotest OK 0.17s
6/120 DPDK:fast-tests / bitmap_autotest OK 0.17s
7/120 DPDK:fast-tests / bitops_autotest OK 1.67s
8/120 DPDK:fast-tests / bitratestats_autotest OK 0.17s
9/120 DPDK:fast-tests / bitset_autotest OK 1.33s
10/120 DPDK:fast-tests / bpf_autotest OK 0.16s
11/120 DPDK:fast-tests / bpf_convert_autotest OK 0.17s
12/120 DPDK:fast-tests / byteorder_autotest OK 0.17s
13/120 DPDK:fast-tests / cfgfile_autotest OK 0.17s
14/120 DPDK:fast-tests / cksum_autotest OK 0.16s
15/120 DPDK:fast-tests / cmdline_autotest OK 0.17s
16/120 DPDK:fast-tests / common_autotest OK 0.42s
17/120 DPDK:fast-tests / compressdev_autotest SKIP 0.14s exit status 77
18/120 DPDK:fast-tests / cpuflags_autotest OK 0.17s
19/120 DPDK:fast-tests / crc_autotest OK 0.17s
20/120 DPDK:fast-tests / user_delay_us OK 0.16s
21/120 DPDK:fast-tests / debug_autotest OK 0.40s
22/120 DPDK:fast-tests / devargs_autotest OK 0.16s
23/120 DPDK:fast-tests / dispatcher_autotest SKIP 0.14s exit status 77
24/120 DPDK:fast-tests / distributor_autotest OK 0.86s
25/120 DPDK:fast-tests / eal_flags_c_opt_autotest OK 0.74s
26/120 DPDK:fast-tests / eal_flags_main_opt_autotest OK 0.28s
27/120 DPDK:fast-tests / eal_flags_n_opt_autotest OK 0.46s
28/120 DPDK:fast-tests / eal_flags_hpet_autotest OK 0.20s
29/120 DPDK:fast-tests / eal_flags_no_huge_autotest OK 0.49s
30/120 DPDK:fast-tests / eal_flags_a_opt_autotest OK 0.42s
31/120 DPDK:fast-tests / eal_flags_b_opt_autotest OK 0.38s
32/120 DPDK:fast-tests / eal_flags_vdev_opt_autotest OK 0.58s
33/120 DPDK:fast-tests / eal_flags_r_opt_autotest OK 0.27s
34/120 DPDK:fast-tests / eal_flags_mem_autotest OK 0.77s
35/120 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 3.08s
36/120 DPDK:fast-tests / eal_flags_misc_autotest OK 2.06s
37/120 DPDK:fast-tests / eal_fs_autotest OK 0.17s
38/120 DPDK:fast-tests / errno_autotest OK 0.17s
39/120 DPDK:fast-tests / ethdev_link_status OK 0.17s
40/120 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 0.49s
41/120 DPDK:fast-tests / event_ring_autotest OK 0.17s
42/120 DPDK:fast-tests / eventdev_common_autotest OK 0.17s
43/120 DPDK:fast-tests / eventdev_selftest_sw OK 0.21s
44/120 DPDK:fast-tests / fbarray_autotest OK 0.17s
45/120 DPDK:fast-tests / fib_autotest OK 0.73s
46/120 DPDK:fast-tests / fib6_autotest OK 0.58s
47/120 DPDK:fast-tests / func_reentrancy_autotest OK 0.50s
48/120 DPDK:fast-tests / graph_autotest OK 0.18s
49/120 DPDK:fast-tests / node_list_dump OK 0.17s
50/120 DPDK:fast-tests / hash_autotest OK 0.28s
51/120 DPDK:fast-tests / hash_readwrite_func_autotest SKIP 0.14s exit status 77
52/120 DPDK:fast-tests / interrupt_autotest OK 1.20s
53/120 DPDK:fast-tests / ipfrag_autotest OK 0.14s
54/120 DPDK:fast-tests / ipsec_autotest SKIP 0.17s exit status 77
55/120 DPDK:fast-tests / kvargs_autotest OK 0.17s
56/120 DPDK:fast-tests / latencystats_autotest OK 0.17s
57/120 DPDK:fast-tests / lcore_var_autotest OK 0.31s
58/120 DPDK:fast-tests / lcores_autotest OK 24.20s
59/120 DPDK:fast-tests / logs_autotest OK 0.17s
60/120 DPDK:fast-tests / lpm_autotest OK 1.50s
61/120 DPDK:fast-tests / lpm6_autotest OK 2.56s
62/120 DPDK:fast-tests / malloc_autotest OK 0.35s
63/120 DPDK:fast-tests / mbuf_autotest OK 0.17s
64/120 DPDK:fast-tests / mcslock_autotest OK 0.40s
65/120 DPDK:fast-tests / member_autotest OK 0.85s
66/120 DPDK:fast-tests / memcpy_autotest OK 2.09s
67/120 DPDK:fast-tests / memory_autotest OK 0.14s
68/120 DPDK:fast-tests / mempool_autotest OK 0.42s
69/120 DPDK:fast-tests / memzone_autotest OK 0.15s
70/120 DPDK:fast-tests / meter_autotest OK 0.17s
71/120 DPDK:fast-tests / metrics_autotest OK 0.17s
72/120 DPDK:fast-tests / multiprocess_autotest OK 0.25s
73/120 DPDK:fast-tests / net_ether_autotest OK 0.47s
74/120 DPDK:fast-tests / net_ipv6_autotest OK 0.17s
75/120 DPDK:fast-tests / pcapng_autotest OK 7.44s
76/120 DPDK:fast-tests / pdcp_autotest SKIP 0.14s exit status 77
77/120 DPDK:fast-tests / pdump_autotest OK 0.30s
78/120 DPDK:fast-tests / per_lcore_autotest OK 0.27s
79/120 DPDK:fast-tests / pflock_autotest OK 0.27s
80/120 DPDK:fast-tests / pie_autotest OK 0.17s
81/120 DPDK:fast-tests / ring_pmd_autotest OK 0.17s
82/120 DPDK:fast-tests / pmu_autotest FAIL 0.17s (exit status 255 or signal 127 SIGinvalid)
>>> MALLOC_PERTURB_=66 DPDK_TEST=pmu_autotest /root/workspace/Generic-Unit-Test-DPDK/dpdk/build/app/dpdk-test --no-huge -m 2048
83/120 DPDK:fast-tests / power_autotest OK 0.17s
84/120 DPDK:fast-tests / power_cpufreq_autotest SKIP 0.14s exit status 77
85/120 DPDK:fast-tests / power_intel_uncore_autotest SKIP 0.17s exit status 77
86/120 DPDK:fast-tests / power_kvm_vm_autotest SKIP 0.14s exit status 77
87/120 DPDK:fast-tests / prefetch_autotest OK 0.17s
88/120 DPDK:fast-tests / ptr_compress_autotest OK 0.17s
89/120 DPDK:fast-tests / rawdev_autotest OK 0.17s
90/120 DPDK:fast-tests / rcu_qsbr_autotest OK 0.26s
91/120 DPDK:fast-tests / reorder_autotest OK 0.28s
92/120 DPDK:fast-tests / rib_autotest OK 3.38s
93/120 DPDK:fast-tests / rib6_autotest OK 3.21s
94/120 DPDK:fast-tests / ring_autotest OK 0.17s
95/120 DPDK:fast-tests / rwlock_test1_autotest OK 0.27s
96/120 DPDK:fast-tests / rwlock_rda_autotest OK 5.17s
97/120 DPDK:fast-tests / rwlock_rds_wrm_autotest OK 5.17s
98/120 DPDK:fast-tests / rwlock_rde_wro_autotest OK 5.17s
99/120 DPDK:fast-tests / sched_autotest OK 0.17s
100/120 DPDK:fast-tests / security_autotest OK 0.14s
101/120 DPDK:fast-tests / seqlock_autotest SKIP 0.17s exit status 77
102/120 DPDK:fast-tests / service_autotest OK 0.27s
103/120 DPDK:fast-tests / soring_autotest OK 0.17s
104/120 DPDK:fast-tests / spinlock_autotest OK 0.18s
105/120 DPDK:fast-tests / stack_autotest OK 0.18s
106/120 DPDK:fast-tests / stack_lf_autotest OK 0.23s
107/120 DPDK:fast-tests / string_autotest OK 0.17s
108/120 DPDK:fast-tests / table_autotest OK 4.47s
109/120 DPDK:fast-tests / tailq_autotest OK 0.17s
110/120 DPDK:fast-tests / telemetry_data_autotest OK 0.17s
111/120 DPDK:fast-tests / telemetry_json_autotest OK 0.17s
112/120 DPDK:fast-tests / thash_autotest OK 0.17s
113/120 DPDK:fast-tests / threads_autotest OK 0.33s
114/120 DPDK:fast-tests / ticketlock_autotest OK 0.18s
115/120 DPDK:fast-tests / timer_autotest OK 2.48s
116/120 DPDK:fast-tests / trace_autotest OK 0.17s
117/120 DPDK:fast-tests / trace_autotest_with_traces OK 0.17s
118/120 DPDK:fast-tests / vdev_autotest OK 0.17s
119/120 DPDK:fast-tests / version_autotest OK 0.17s
120/120 DPDK:fast-tests / telemetry_all SKIP 0.01s exit status 77
Ok: 109
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 10
Timeout: 0
Full log written to /root/workspace/Generic-Unit-Test-DPDK/dpdk/build/meson-logs/testlog.txt
Test log output from the failed test pmu_autotest:
Sorry, we were not able to find the logs for this test.
Download the log output from the CI site for this test run.
==== End log output ====
Debian Bullseye
Kernel: Depends on container host
Compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110
CentOS Stream 9
Kernel: Depends on container host
Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)
Fedora 40
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)
RHEL9
Kernel: Depends on container host
Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)
Fedora 40 (Clang)
Kernel: Depends on container host
Compiler: clang 18.1.8 (Fedora 18.1.8-1.fc40)
Fedora 41
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)
RHEL8
Kernel: Depends on container host
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-22)
Debian 12
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
Fedora 41 (Clang)
Kernel: Depends on container host
Compiler: clang 19.1.5 (Fedora 19.1.5-1.fc41)
Ubuntu 22.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Ubuntu 24.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
Ubuntu 20.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32353/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2025-01-17 11:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250117090033.2807073-5-tduszynski@marvell.com>
2025-01-17 8:31 ` |SUCCESS| pw150159-150162 [PATCH v17 4/4] eal: add PMU support to tracing library qemudev
2025-01-17 8:35 ` qemudev
2025-01-17 9:02 ` |SUCCESS| pw150162 " checkpatch
2025-01-17 10:04 ` |FAILURE| " 0-day Robot
2025-01-17 10:53 ` |SUCCESS| pw150159-150162 [PATCH] [v17,4/4] eal: add PMU support to dpdklab
2025-01-17 10:53 ` dpdklab
2025-01-17 10:54 ` dpdklab
2025-01-17 10:54 ` dpdklab
2025-01-17 10:56 ` dpdklab
2025-01-17 11:00 ` dpdklab
2025-01-17 11:00 ` dpdklab [this message]
2025-01-17 11:03 ` dpdklab
2025-01-17 11:04 ` dpdklab
2025-01-17 11:04 ` dpdklab
2025-01-17 11:11 ` |FAILURE| " dpdklab
2025-01-17 11:28 ` |SUCCESS| " dpdklab
2025-01-17 11:28 ` dpdklab
2025-01-17 11:30 ` |PENDING| " dpdklab
2025-01-17 11:33 ` |FAILURE| " dpdklab
2025-01-17 11:35 ` dpdklab
2025-01-17 11:44 ` dpdklab
2025-01-17 11:48 ` |WARNING| " dpdklab
2025-01-17 11:50 ` dpdklab
2025-01-17 11:50 ` |FAILURE| " dpdklab
2025-01-17 11:51 ` dpdklab
2025-01-17 11:58 ` |SUCCESS| " dpdklab
2025-01-17 12:05 ` |WARNING| " dpdklab
2025-01-17 13:04 ` |FAILURE| " dpdklab
2025-01-17 13:43 ` |SUCCESS| " dpdklab
2025-01-17 16:00 ` 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=678a3838.050a0220.2d6320.7db8SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=tduszynski@marvell.com \
--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).