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,
	Bruce Richardson <bruce.richardson@intel.com>
Subject: |FAILURE| pw154848 [PATCH] node: fix C++ compatibility errors (optio
Date: Mon, 30 Jun 2025 09:11:59 -0700 (PDT)	[thread overview]
Message-ID: <6862b74f.050a0220.67ebd.ee31SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250630104939.2265866-2-bruce.richardson@intel.com>

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

_Testing issues_

Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Monday, June 30 2025 10:49:40 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:20460dcffd08a4680f881c39916ae783ee830374

154848 --> testing issues

Upstream job id: Generic-Unit-Test-DPDK#351094

Test environment and result as below:

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

==== Unit test summary for Ubuntu 24.04 (dpdk_unit_test): ====
ninja: Entering directory `/root/workspace/Generic-Unit-Test-DPDK/dpdk/build'
ninja: no work to do.
  1/121 DPDK:fast-tests / acl_autotest                   OK              19.10s
  2/121 DPDK:fast-tests / alarm_autotest                 OK               1.32s
  3/121 DPDK:fast-tests / argparse_autotest              OK               0.67s
  4/121 DPDK:fast-tests / atomic_autotest                OK               3.20s
  5/121 DPDK:fast-tests / bitcount_autotest              OK               5.63s
  6/121 DPDK:fast-tests / bitmap_autotest                OK               2.95s
  7/121 DPDK:fast-tests / bitops_autotest                OK               4.17s
  8/121 DPDK:fast-tests / bitratestats_autotest          OK               0.18s
  9/121 DPDK:fast-tests / bitset_autotest                OK               3.39s
 10/121 DPDK:fast-tests / bpf_autotest                   OK               0.39s
 11/121 DPDK:fast-tests / bpf_convert_autotest           OK               0.22s
 12/121 DPDK:fast-tests / byteorder_autotest             OK               0.23s
 13/121 DPDK:fast-tests / cfgfile_autotest               OK               0.61s
 14/121 DPDK:fast-tests / cksum_autotest                 OK               1.09s
 15/121 DPDK:fast-tests / cmdline_autotest               OK               0.63s
 16/121 DPDK:fast-tests / common_autotest                OK               2.23s
 17/121 DPDK:fast-tests / compressdev_autotest           SKIP             0.45s   exit status 77
 18/121 DPDK:fast-tests / cpuflags_autotest              OK               0.37s
 19/121 DPDK:fast-tests / crc_autotest                   OK               0.69s
 20/121 DPDK:fast-tests / user_delay_us                  OK               0.54s
 21/121 DPDK:fast-tests / debug_autotest                 OK               2.37s
 22/121 DPDK:fast-tests / devargs_autotest               OK               0.54s
 23/121 DPDK:fast-tests / dispatcher_autotest            SKIP             0.15s   exit status 77
 24/121 DPDK:fast-tests / distributor_autotest           OK              14.77s
 25/121 DPDK:fast-tests / eal_flags_c_opt_autotest       OK               9.05s
 26/121 DPDK:fast-tests / eal_flags_main_opt_autotest    OK               0.44s
 27/121 DPDK:fast-tests / eal_flags_n_opt_autotest       OK               0.55s
 28/121 DPDK:fast-tests / eal_flags_hpet_autotest        OK               0.65s
 29/121 DPDK:fast-tests / eal_flags_no_huge_autotest     OK               0.72s
 30/121 DPDK:fast-tests / eal_flags_a_opt_autotest       OK               0.70s
 31/121 DPDK:fast-tests / eal_flags_b_opt_autotest       OK               0.33s
 32/121 DPDK:fast-tests / eal_flags_vdev_opt_autotest    OK               0.57s
 33/121 DPDK:fast-tests / eal_flags_r_opt_autotest       OK               0.27s
 34/121 DPDK:fast-tests / eal_flags_mem_autotest         OK               0.87s
 35/121 DPDK:fast-tests / eal_flags_file_prefix_autotest OK               4.87s
 36/121 DPDK:fast-tests / eal_flags_misc_autotest        OK               5.27s
 37/121 DPDK:fast-tests / eal_fs_autotest                OK               0.70s
 38/121 DPDK:fast-tests / errno_autotest                 OK               0.33s
 39/121 DPDK:fast-tests / ethdev_link_status             OK               0.89s
 40/121 DPDK:fast-tests / event_eth_tx_adapter_autotest  OK               0.88s
 41/121 DPDK:fast-tests / event_ring_autotest            OK               0.29s
 42/121 DPDK:fast-tests / event_vector_adapter_autotest  FAIL             3.39s   (exit status 255 or signal 127 SIGinvalid)
>>> MALLOC_PERTURB_=53 DPDK_TEST=event_vector_adapter_autotest /root/workspace/Generic-Unit-Test-DPDK/dpdk/build/app/dpdk-test --no-huge -m 2048

 43/121 DPDK:fast-tests / eventdev_common_autotest       OK               1.18s
 44/121 DPDK:fast-tests / eventdev_selftest_sw           OK               0.77s
 45/121 DPDK:fast-tests / fbarray_autotest               OK               0.49s
 46/121 DPDK:fast-tests / fib_autotest                   OK               4.07s
 47/121 DPDK:fast-tests / fib6_autotest                  OK               2.02s
 48/121 DPDK:fast-tests / func_reentrancy_autotest       OK               1.87s
 49/121 DPDK:fast-tests / graph_autotest                 OK               0.19s
 50/121 DPDK:fast-tests / node_list_dump                 OK               0.25s
 51/121 DPDK:fast-tests / graph_feature_arc_autotest     OK               0.21s
 52/121 DPDK:fast-tests / hash_autotest                  OK               0.49s
 53/121 DPDK:fast-tests / hash_readwrite_func_autotest   SKIP             0.15s   exit status 77
 54/121 DPDK:fast-tests / interrupt_autotest             OK               1.29s
 55/121 DPDK:fast-tests / ipfrag_autotest                OK               0.15s
 56/121 DPDK:fast-tests / ipsec_autotest                 SKIP             0.19s   exit status 77
 57/121 DPDK:fast-tests / kvargs_autotest                OK               0.18s
 58/121 DPDK:fast-tests / latencystats_autotest          OK               0.20s
 59/121 DPDK:fast-tests / lcore_var_autotest             OK               0.31s
 60/121 DPDK:fast-tests / lcores_autotest                OK               1.67s
 61/121 DPDK:fast-tests / logs_autotest                  OK               0.22s
 62/121 DPDK:fast-tests / lpm_autotest                   OK               3.44s
 63/121 DPDK:fast-tests / lpm6_autotest                  OK               5.05s
 64/121 DPDK:fast-tests / malloc_autotest                OK               0.58s
 65/121 DPDK:fast-tests / mbuf_autotest                  OK               0.38s
 66/121 DPDK:fast-tests / mcslock_autotest               OK               0.97s
 67/121 DPDK:fast-tests / member_autotest                OK               1.06s
 68/121 DPDK:fast-tests / memcpy_autotest                OK               6.00s
 69/121 DPDK:fast-tests / memory_autotest                OK               0.24s
 70/121 DPDK:fast-tests / mempool_autotest               OK               0.69s
 71/121 DPDK:fast-tests / memzone_autotest               OK               0.52s
 72/121 DPDK:fast-tests / meter_autotest                 OK               0.77s
 73/121 DPDK:fast-tests / metrics_autotest               OK               0.30s
 74/121 DPDK:fast-tests / multiprocess_autotest          OK               1.03s
 75/121 DPDK:fast-tests / net_ether_autotest             OK               1.21s
 76/121 DPDK:fast-tests / net_ipv6_autotest              OK               0.40s
 77/121 DPDK:fast-tests / pcapng_autotest                OK               8.78s
 78/121 DPDK:fast-tests / pdcp_autotest                  SKIP             0.30s   exit status 77
 79/121 DPDK:fast-tests / pdump_autotest                 OK               0.55s
 80/121 DPDK:fast-tests / per_lcore_autotest             OK               0.39s
 81/121 DPDK:fast-tests / pflock_autotest                OK               0.86s
 82/121 DPDK:fast-tests / pie_autotest                   OK               0.34s
 83/121 DPDK:fast-tests / ring_pmd_autotest              OK               0.57s
 84/121 DPDK:fast-tests / power_autotest                 OK               0.52s
 85/121 DPDK:fast-tests / power_cpufreq_autotest         SKIP             0.97s   exit status 77
 86/121 DPDK:fast-tests / power_intel_uncore_autotest    SKIP             4.05s   exit status 77
 87/121 DPDK:fast-tests / power_kvm_vm_autotest          SKIP             0.23s   exit status 77
 88/121 DPDK:fast-tests / prefetch_autotest              OK               0.77s
 89/121 DPDK:fast-tests / ptr_compress_autotest          OK               0.42s
 90/121 DPDK:fast-tests / rawdev_autotest                OK               0.51s
 91/121 DPDK:fast-tests / rcu_qsbr_autotest              OK               0.62s
 92/121 DPDK:fast-tests / reorder_autotest               OK               0.47s
 93/121 DPDK:fast-tests / rib_autotest                   OK               6.69s
 94/121 DPDK:fast-tests / rib6_autotest                  OK              11.89s
 95/121 DPDK:fast-tests / ring_autotest                  OK               0.19s
 96/121 DPDK:fast-tests / rwlock_test1_autotest          OK               0.28s
 97/121 DPDK:fast-tests / rwlock_rda_autotest            OK               6.01s
 98/121 DPDK:fast-tests / rwlock_rds_wrm_autotest        OK               6.31s
 99/121 DPDK:fast-tests / rwlock_rde_wro_autotest        OK               5.63s
100/121 DPDK:fast-tests / sched_autotest                 OK               2.49s
101/121 DPDK:fast-tests / security_autotest              OK               0.28s
102/121 DPDK:fast-tests / seqlock_autotest               SKIP             0.49s   exit status 77
103/121 DPDK:fast-tests / service_autotest               OK               0.49s
104/121 DPDK:fast-tests / soring_autotest                OK               0.30s
105/121 DPDK:fast-tests / spinlock_autotest              OK               0.18s
106/121 DPDK:fast-tests / stack_autotest                 OK               0.18s
107/121 DPDK:fast-tests / stack_lf_autotest              OK               0.26s
108/121 DPDK:fast-tests / string_autotest                OK               0.28s
109/121 DPDK:fast-tests / table_autotest                 OK              13.91s
110/121 DPDK:fast-tests / tailq_autotest                 OK               0.19s
111/121 DPDK:fast-tests / telemetry_data_autotest        OK               0.22s
112/121 DPDK:fast-tests / telemetry_json_autotest        OK               0.18s
113/121 DPDK:fast-tests / thash_autotest                 OK               0.20s
114/121 DPDK:fast-tests / threads_autotest               OK               0.44s
115/121 DPDK:fast-tests / ticketlock_autotest            OK               0.35s
116/121 DPDK:fast-tests / timer_autotest                 OK               3.42s
117/121 DPDK:fast-tests / trace_autotest                 OK               3.69s
118/121 DPDK:fast-tests / trace_autotest_with_traces     OK               0.89s
119/121 DPDK:fast-tests / vdev_autotest                  OK               0.35s
120/121 DPDK:fast-tests / version_autotest               OK               0.28s
121/121 DPDK:fast-tests / telemetry_all                  OK               1.08s


Ok:                 111 
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 ====

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

CentOS Stream 9
	Kernel: 5.15
	Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-7)

CentOS Stream 10
	Kernel: 5.15
	Compiler: gcc gcc (GCC) 14.2.1 20250110 (Red Hat 14.2.1-8)

Fedora Linux 40
	Kernel: 5.15
	Compiler: gcc gcc (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3)

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

Fedora Linux 41
	Kernel: 5.15
	Compiler: gcc gcc (GCC) 14.3.1 20250523 (Red Hat 14.3.1-1)

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

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

Ubuntu 20.04
	Kernel: 5.15
	Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.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/33541/

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-30 16:12 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250630104939.2265866-2-bruce.richardson@intel.com>
2025-06-30 10:31 ` |SUCCESS| pw154848 [PATCH] node: fix C++ compatibility errors (option 1) qemudev
2025-06-30 10:36 ` qemudev
2025-06-30 10:50 ` |WARNING| pw154848 [PATCH] node: fix C++ compatibility errors option 1 checkpatch
2025-06-30 12:03 ` |SUCCESS| pw154848 [PATCH] node: fix C++ compatibility errors (option 1) 0-day Robot
2025-06-30 13:47 ` |SUCCESS| pw154848 [PATCH] node: fix C++ compatibility errors (optio dpdklab
2025-06-30 13:47 ` dpdklab
2025-06-30 13:50 ` |FAILURE| " dpdklab
2025-06-30 13:57 ` |SUCCESS| " dpdklab
2025-06-30 14:01 ` dpdklab
2025-06-30 14:10 ` dpdklab
2025-06-30 14:22 ` dpdklab
2025-06-30 14:56 ` |PENDING| " dpdklab
2025-06-30 15:17 ` dpdklab
2025-06-30 15:17 ` dpdklab
2025-06-30 15:27 ` dpdklab
2025-06-30 16:03 ` dpdklab
2025-06-30 16:11 ` dpdklab [this message]
2025-06-30 16:16 ` |FAILURE| " dpdklab
2025-06-30 16:17 ` dpdklab
2025-06-30 17:16 ` |SUCCESS| " dpdklab
2025-06-30 17:24 ` dpdklab
2025-06-30 18:32 ` dpdklab
2025-06-30 18:33 ` dpdklab
2025-06-30 18:33 ` dpdklab
2025-06-30 18:34 ` |WARNING| " dpdklab
2025-06-30 18:35 ` dpdklab
2025-06-30 19:18 ` dpdklab
2025-06-30 19:18 ` dpdklab
2025-06-30 19:19 ` dpdklab
2025-06-30 19:20 ` dpdklab
2025-06-30 19:20 ` dpdklab
2025-06-30 19:21 ` dpdklab
2025-06-30 23:56 ` |SUCCESS| " 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=6862b74f.050a0220.67ebd.ee31SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=bruce.richardson@intel.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).