automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
	David Marchand <david.marchand@redhat.com>
Subject: |FAILURE| pw154259-154260 [PATCH] [2/2] test/lcore: fix build with M
Date: Tue, 10 Jun 2025 05:43:34 -0700 (PDT)	[thread overview]
Message-ID: <68482876.920a0220.2af79e.8cbcSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250610083643.8466-2-david.marchand@redhat.com>

Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/154260

_Testing issues_

Submitter: David Marchand <david.marchand@redhat.com>
Date: Tuesday, June 10 2025 08:36:42 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:b1f3a7a8c375fbb66be48aed078222686d16fdb5

154259-154260 --> testing issues

Upstream job id: Generic-VM-Unit-Test-DPDK#29076

Test environment and result as below:

+-------------------------------+----------------+
|          Environment          | dpdk_unit_test |
+===============================+================+
| CentOS Stream 10              | PASS           |
+-------------------------------+----------------+
| CentOS Stream 9               | PASS           |
+-------------------------------+----------------+
| Debian GNU/Linux 12           | PASS           |
+-------------------------------+----------------+
| Fedora 40                     | PASS           |
+-------------------------------+----------------+
| Fedora 41                     | PASS           |
+-------------------------------+----------------+
| Fedora 40 (Clang)             | PASS           |
+-------------------------------+----------------+
| Red Hat Enterprise Linux 8.10 | PASS           |
+-------------------------------+----------------+
| Fedora 41 (Clang)             | PASS           |
+-------------------------------+----------------+
| Red Hat Enterprise Linux 9.5  | PASS           |
+-------------------------------+----------------+
| Ubuntu 20.04                  | PASS           |
+-------------------------------+----------------+
| Ubuntu 22.04                  | FAIL           |
+-------------------------------+----------------+
| Ubuntu 24.04                  | PASS           |
+-------------------------------+----------------+
| Windows Server 2022           | PASS           |
+-------------------------------+----------------+

==== Unit test summary for Ubuntu 22.04 (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               4.44s
  2/120 DPDK:fast-tests / alarm_autotest                 OK               1.22s
  3/120 DPDK:fast-tests / argparse_autotest              OK               0.40s
  4/120 DPDK:fast-tests / atomic_autotest                OK               0.54s
  5/120 DPDK:fast-tests / bitcount_autotest              OK               0.18s
  6/120 DPDK:fast-tests / bitmap_autotest                OK               0.34s
  7/120 DPDK:fast-tests / bitops_autotest                OK               2.12s
  8/120 DPDK:fast-tests / bitratestats_autotest          OK               0.31s
  9/120 DPDK:fast-tests / bitset_autotest                OK               2.04s
 10/120 DPDK:fast-tests / bpf_autotest                   OK               0.29s
 11/120 DPDK:fast-tests / bpf_convert_autotest           OK               0.31s
 12/120 DPDK:fast-tests / byteorder_autotest             OK               0.31s
 13/120 DPDK:fast-tests / cfgfile_autotest               OK               0.32s
 14/120 DPDK:fast-tests / cksum_autotest                 OK               0.17s
 15/120 DPDK:fast-tests / cmdline_autotest               OK               0.27s
 16/120 DPDK:fast-tests / common_autotest                OK               0.81s
 17/120 DPDK:fast-tests / compressdev_autotest           SKIP             0.15s   exit status 77
 18/120 DPDK:fast-tests / cpuflags_autotest              OK               0.28s
 19/120 DPDK:fast-tests / crc_autotest                   OK               0.21s
 20/120 DPDK:fast-tests / user_delay_us                  OK               0.17s
 21/120 DPDK:fast-tests / debug_autotest                 OK               0.69s
 22/120 DPDK:fast-tests / devargs_autotest               OK               0.25s
 23/120 DPDK:fast-tests / dispatcher_autotest            SKIP             0.28s   exit status 77
 24/120 DPDK:fast-tests / distributor_autotest           OK               1.41s
 25/120 DPDK:fast-tests / eal_flags_c_opt_autotest       OK               1.28s
 26/120 DPDK:fast-tests / eal_flags_main_opt_autotest    OK               0.45s
 27/120 DPDK:fast-tests / eal_flags_n_opt_autotest       OK               0.72s
 28/120 DPDK:fast-tests / eal_flags_hpet_autotest        OK               0.31s
 29/120 DPDK:fast-tests / eal_flags_no_huge_autotest     OK               0.70s
 30/120 DPDK:fast-tests / eal_flags_a_opt_autotest       OK               0.53s
 31/120 DPDK:fast-tests / eal_flags_b_opt_autotest       OK               0.44s
 32/120 DPDK:fast-tests / eal_flags_vdev_opt_autotest    OK               0.77s
 33/120 DPDK:fast-tests / eal_flags_r_opt_autotest       OK               0.31s
 34/120 DPDK:fast-tests / eal_flags_mem_autotest         OK               1.13s
 35/120 DPDK:fast-tests / eal_flags_file_prefix_autotest OK               4.22s
 36/120 DPDK:fast-tests / eal_flags_misc_autotest        OK               3.09s
 37/120 DPDK:fast-tests / eal_fs_autotest                OK               0.29s
 38/120 DPDK:fast-tests / errno_autotest                 OK               0.26s
 39/120 DPDK:fast-tests / ethdev_link_status             OK               0.17s
 40/120 DPDK:fast-tests / event_eth_tx_adapter_autotest  OK               0.68s
 41/120 DPDK:fast-tests / event_ring_autotest            OK               0.31s
 42/120 DPDK:fast-tests / event_vector_adapter_autotest  FAIL            11.06s   killed by signal 11 SIGSEGV
>>> DPDK_TEST=event_vector_adapter_autotest MALLOC_PERTURB_=88 /root/workspace/Generic-Unit-Test-DPDK/dpdk/build/app/dpdk-test --no-huge -m 2048

 43/120 DPDK:fast-tests / eventdev_common_autotest       OK               0.18s
 44/120 DPDK:fast-tests / eventdev_selftest_sw           OK               0.32s
 45/120 DPDK:fast-tests / fbarray_autotest               OK               0.34s
 46/120 DPDK:fast-tests / fib_autotest                   OK               1.08s
 47/120 DPDK:fast-tests / fib6_autotest                  OK               1.09s
 48/120 DPDK:fast-tests / func_reentrancy_autotest       OK               0.79s
 49/120 DPDK:fast-tests / graph_autotest                 OK               0.31s
 50/120 DPDK:fast-tests / node_list_dump                 OK               0.19s
 51/120 DPDK:fast-tests / hash_autotest                  OK               0.47s
 52/120 DPDK:fast-tests / hash_readwrite_func_autotest   SKIP             0.22s   exit status 77
 53/120 DPDK:fast-tests / interrupt_autotest             OK               1.78s
 54/120 DPDK:fast-tests / ipfrag_autotest                OK               0.15s
 55/120 DPDK:fast-tests / ipsec_autotest                 SKIP             0.30s   exit status 77
 56/120 DPDK:fast-tests / kvargs_autotest                OK               0.19s
 57/120 DPDK:fast-tests / latencystats_autotest          OK               0.29s
 58/120 DPDK:fast-tests / lcore_var_autotest             OK               0.51s
 59/120 DPDK:fast-tests / lcores_autotest                OK               1.39s
 60/120 DPDK:fast-tests / logs_autotest                  OK               0.31s
 61/120 DPDK:fast-tests / lpm_autotest                   OK               2.47s
 62/120 DPDK:fast-tests / lpm6_autotest                  OK               4.47s
 63/120 DPDK:fast-tests / malloc_autotest                OK               0.67s
 64/120 DPDK:fast-tests / mbuf_autotest                  OK               0.29s
 65/120 DPDK:fast-tests / mcslock_autotest               OK               0.70s
 66/120 DPDK:fast-tests / member_autotest                OK               1.31s
 67/120 DPDK:fast-tests / memcpy_autotest                OK               3.01s
 68/120 DPDK:fast-tests / memory_autotest                OK               0.15s
 69/120 DPDK:fast-tests / mempool_autotest               OK               0.77s
 70/120 DPDK:fast-tests / memzone_autotest               OK               0.15s
 71/120 DPDK:fast-tests / meter_autotest                 OK               0.31s
 72/120 DPDK:fast-tests / metrics_autotest               OK               0.18s
 73/120 DPDK:fast-tests / multiprocess_autotest          OK               0.40s
 74/120 DPDK:fast-tests / net_ether_autotest             OK               0.73s
 75/120 DPDK:fast-tests / net_ipv6_autotest              OK               0.27s
 76/120 DPDK:fast-tests / pcapng_autotest                OK               7.31s
 77/120 DPDK:fast-tests / pdcp_autotest                  SKIP             0.24s   exit status 77
 78/120 DPDK:fast-tests / pdump_autotest                 OK               0.76s
 79/120 DPDK:fast-tests / per_lcore_autotest             OK               0.29s
 80/120 DPDK:fast-tests / pflock_autotest                OK               0.34s
 81/120 DPDK:fast-tests / pie_autotest                   OK               0.17s
 82/120 DPDK:fast-tests / ring_pmd_autotest              OK               0.23s
 83/120 DPDK:fast-tests / power_autotest                 OK               0.31s
 84/120 DPDK:fast-tests / power_cpufreq_autotest         SKIP             0.15s   exit status 77
 85/120 DPDK:fast-tests / power_intel_uncore_autotest    SKIP             0.31s   exit status 77
 86/120 DPDK:fast-tests / power_kvm_vm_autotest          SKIP             0.27s   exit status 77
 87/120 DPDK:fast-tests / prefetch_autotest              OK               0.18s
 88/120 DPDK:fast-tests / ptr_compress_autotest          OK               0.29s
 89/120 DPDK:fast-tests / rawdev_autotest                OK               0.27s
 90/120 DPDK:fast-tests / rcu_qsbr_autotest              OK               0.42s
 91/120 DPDK:fast-tests / reorder_autotest               OK               0.37s
 92/120 DPDK:fast-tests / rib_autotest                   OK               5.41s
 93/120 DPDK:fast-tests / rib6_autotest                  OK               5.31s
 94/120 DPDK:fast-tests / ring_autotest                  OK               0.18s
 95/120 DPDK:fast-tests / rwlock_test1_autotest          OK               0.32s
 96/120 DPDK:fast-tests / rwlock_rda_autotest            OK               5.22s
 97/120 DPDK:fast-tests / rwlock_rds_wrm_autotest        OK               5.29s
 98/120 DPDK:fast-tests / rwlock_rde_wro_autotest        OK               5.32s
 99/120 DPDK:fast-tests / sched_autotest                 OK               0.29s
100/120 DPDK:fast-tests / security_autotest              OK               0.15s
101/120 DPDK:fast-tests / seqlock_autotest               SKIP             0.32s   exit status 77
102/120 DPDK:fast-tests / service_autotest               OK               0.45s
103/120 DPDK:fast-tests / soring_autotest                OK               0.17s
104/120 DPDK:fast-tests / spinlock_autotest              OK               0.29s
105/120 DPDK:fast-tests / stack_autotest                 OK               0.26s
106/120 DPDK:fast-tests / stack_lf_autotest              OK               0.50s
107/120 DPDK:fast-tests / string_autotest                OK               0.34s
108/120 DPDK:fast-tests / table_autotest                 OK               7.16s
109/120 DPDK:fast-tests / tailq_autotest                 OK               0.24s
110/120 DPDK:fast-tests / telemetry_data_autotest        OK               0.29s
111/120 DPDK:fast-tests / telemetry_json_autotest        OK               0.21s
112/120 DPDK:fast-tests / thash_autotest                 OK               0.18s
113/120 DPDK:fast-tests / threads_autotest               OK               0.38s
114/120 DPDK:fast-tests / ticketlock_autotest            OK               0.29s
115/120 DPDK:fast-tests / timer_autotest                 OK               2.70s
116/120 DPDK:fast-tests / trace_autotest                 OK               0.20s
117/120 DPDK:fast-tests / trace_autotest_with_traces     OK               0.18s
118/120 DPDK:fast-tests / vdev_autotest                  OK               0.38s
119/120 DPDK:fast-tests / version_autotest               OK               0.17s
120/120 DPDK:fast-tests / telemetry_all                  OK               1.28s


Ok:                 110 
Expected Fail:      0   
Fail:               1   
Unexpected Pass:    0   
Skipped:            9   
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 event_vector_adapter_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 ====

CentOS Stream 10
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20241104 (Red Hat 14.2.1-6)

CentOS Stream 9
	Kernel: Depends on container host
	Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)

Debian GNU/Linux 12
	Kernel: 5.15
	Compiler: gcc gcc (Debian 12.2.0-14) 12.2.0

Fedora 40
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)

Fedora 41
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)

Fedora 40 (Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.8 (Fedora 18.1.8-1.fc40)

Red Hat Enterprise Linux 8.10
	Kernel: 5.15
	Compiler: gcc gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-22)

Fedora 41 (Clang)
	Kernel: Depends on container host
	Compiler: clang 19.1.5 (Fedora 19.1.5-1.fc41)

Red Hat Enterprise Linux 9.5
	Kernel: 5.15
	Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-2)

Ubuntu 20.04
	Kernel: 5.15
	Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

Ubuntu 22.04
	Kernel: 5.15
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Ubuntu 24.04
	Kernel: 5.15
	Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0

Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33371/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2025-06-10 12:43 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250610083643.8466-2-david.marchand@redhat.com>
2025-06-10  8:03 ` |SUCCESS| pw154259-154260 [PATCH 2/2] test/lcore: fix build with MSVC qemudev
2025-06-10  8:07 ` qemudev
2025-06-10  8:37 ` |SUCCESS| pw154260 " checkpatch
2025-06-10  9:45 ` 0-day Robot
2025-06-10  9:57 ` |SUCCESS| pw154259-154260 [PATCH] [2/2] test/lcore: fix build with M dpdklab
2025-06-10 10:00 ` dpdklab
2025-06-10 10:28 ` |PENDING| " dpdklab
2025-06-10 11:09 ` |SUCCESS| " dpdklab
2025-06-10 11:24 ` |PENDING| " dpdklab
2025-06-10 11:26 ` dpdklab
2025-06-10 11:29 ` |SUCCESS| " dpdklab
2025-06-10 11:35 ` |PENDING| " dpdklab
2025-06-10 12:27 ` |FAILURE| " dpdklab
2025-06-10 12:43 ` dpdklab [this message]
2025-06-10 13:46 ` |PENDING| " dpdklab
2025-06-10 14:04 ` |WARNING| " dpdklab
2025-06-10 20:27 ` |SUCCESS| " dpdklab
2025-06-10 20:28 ` dpdklab
2025-06-10 23:50 ` dpdklab
2025-06-10 23:50 ` dpdklab
2025-06-10 23:52 ` dpdklab
2025-06-10 23:52 ` dpdklab
2025-06-10 23:53 ` dpdklab
2025-06-10 23:53 ` dpdklab
2025-06-10 23:54 ` dpdklab
2025-06-11 14:01 ` 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=68482876.920a0220.2af79e.8cbcSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --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).