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
Subject: |FAILURE| [GIT MASTER] 2e22572b9a6ce8bcdc0347313a35bb3066b0faff
Date: Sun, 09 Nov 2025 17:55:00 -0800 (PST)	[thread overview]
Message-ID: <691145f4.050a0220.2a6458.f30bSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing issues_

Branch: dpdk

2e22572b9a6ce8bcdc0347313a35bb3066b0faff --> testing issues

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

Test environment and result as below:

+-------------------------------+----------------+
|          Environment          | dpdk_unit_test |
+===============================+================+
| Fedora Linux 42               | PASS           |
+-------------------------------+----------------+
| Red Hat Enterprise Linux 9.5  | PASS           |
+-------------------------------+----------------+
| CentOS Stream 9               | PASS           |
+-------------------------------+----------------+
| Red Hat Enterprise Linux 8.10 | PASS           |
+-------------------------------+----------------+
| Ubuntu 20.04                  | PASS           |
+-------------------------------+----------------+
| CentOS Stream 10              | PASS           |
+-------------------------------+----------------+
| Arch Linux 20250613.0.365270  | PASS           |
+-------------------------------+----------------+
| Fedora Linux 40               | PASS           |
+-------------------------------+----------------+
| Debian GNU/Linux 12           | PASS           |
+-------------------------------+----------------+
| Fedora Linux 41               | PASS           |
+-------------------------------+----------------+
| Ubuntu 24.04                  | FAIL           |
+-------------------------------+----------------+
| Ubuntu 22.04                  | PASS           |
+-------------------------------+----------------+
| 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/120 DPDK:fast-tests / acl_autotest                   OK               2.39s
  2/120 DPDK:fast-tests / alarm_autotest                 OK               1.17s
  3/120 DPDK:fast-tests / argparse_autotest              OK               0.16s
  4/120 DPDK:fast-tests / atomic_autotest                OK               0.33s
  5/120 DPDK:fast-tests / bitcount_autotest              OK               0.17s
  6/120 DPDK:fast-tests / bitmap_autotest                OK               0.16s
  7/120 DPDK:fast-tests / bitops_autotest                OK               1.66s
  8/120 DPDK:fast-tests / bitratestats_autotest          OK               0.17s
  9/120 DPDK:fast-tests / bitset_autotest                OK               1.39s
 10/120 DPDK:fast-tests / bpf_autotest                   OK               0.18s
 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.16s
 14/120 DPDK:fast-tests / cksum_autotest                 OK               0.16s
 15/120 DPDK:fast-tests / cmdline_autotest               OK               0.16s
 16/120 DPDK:fast-tests / common_autotest                OK               0.48s
 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.16s
 20/120 DPDK:fast-tests / user_delay_us                  OK               0.16s
 21/120 DPDK:fast-tests / debug_autotest                 OK               1.39s
 22/120 DPDK:fast-tests / devargs_autotest               OK               0.28s
 23/120 DPDK:fast-tests / dispatcher_autotest            SKIP             0.22s   exit status 77
 24/120 DPDK:fast-tests / distributor_autotest           OK               1.17s
 25/120 DPDK:fast-tests / eal_flags_c_opt_autotest       OK               0.89s
 26/120 DPDK:fast-tests / eal_flags_main_opt_autotest    OK               0.29s
 27/120 DPDK:fast-tests / eal_flags_n_opt_autotest       OK               0.52s
 28/120 DPDK:fast-tests / eal_flags_hpet_autotest        OK               0.20s
 29/120 DPDK:fast-tests / eal_flags_no_huge_autotest     OK               0.45s
 30/120 DPDK:fast-tests / eal_flags_a_opt_autotest       OK               0.36s
 31/120 DPDK:fast-tests / eal_flags_b_opt_autotest       OK               0.40s
 32/120 DPDK:fast-tests / eal_flags_vdev_opt_autotest    OK               0.55s
 33/120 DPDK:fast-tests / eal_flags_r_opt_autotest       OK               0.25s
 34/120 DPDK:fast-tests / eal_flags_mem_autotest         OK               0.69s
 35/120 DPDK:fast-tests / eal_flags_file_prefix_autotest OK               2.05s


Ok:                 33  
Expected Fail:      0   
Fail:               0   
Unexpected Pass:    0   
Skipped:            2   
Timeout:            0   

Full log written to /root/workspace/Generic-Unit-Test-DPDK/dpdk/build/meson-logs/testlog.txt

==== End log output ====

Fedora Linux 42
	Kernel: 5.15
	Compiler: gcc gcc (GCC) 15.2.1 20250808 (Red Hat 15.2.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)

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

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

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

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

Arch Linux 20250613.0.365270
	Kernel: 5.15
	Compiler: gcc gcc (GCC) 15.1.1 20250425

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

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

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

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

Ubuntu 22.04
	Kernel: 5.15
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.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/tarballs/35515/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2025-11-10  1:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-10  1:55 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-11-10  1:49 dpdklab
2025-11-10  1:35 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=691145f4.050a0220.2a6458.f30bSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --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).