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, Shani Peretz <shperetz@nvidia.com>
Subject: |FAILURE| pw159643 [PATCH] net/mlx5: add RSS TIR registration API
Date: Sun, 11 Jan 2026 19:54:56 -0800 (PST)	[thread overview]
Message-ID: <69647090.050a0220.3393d1.cac2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20260108081232.5420-1-shperetz@nvidia.com>

Test-Label: iol-compile-arm64-testing
Test-Status: FAILURE
http://dpdk.org/patch/159643

_Testing issues_

Submitter: Shani Peretz <shperetz@nvidia.com>
Date: Thursday, January 08 2026 08:12:31 
DPDK git baseline: Repo:dpdk-next-net-mlx
  Branch: master
  CommitID:1b8a03f181d93c751ebea9df1584628f485ec745

159643 --> testing issues

Upstream job id: Generic-DPDK-Compile-Meson#455304

Test environment and result as below:

+-------------------------------+--------------------+
|          Environment          | dpdk_meson_compile |
+===============================+====================+
| Red Hat Enterprise Linux 9.7  | PASS               |
+-------------------------------+--------------------+
| Red Hat Enterprise Linux 10.1 | PASS               |
+-------------------------------+--------------------+
| Ubuntu 24.04                  | FAIL               |
+-------------------------------+--------------------+
| Debian GNU/Linux 12           | PASS               |
+-------------------------------+--------------------+
| Fedora Linux 42               | PASS               |
+-------------------------------+--------------------+
| Ubuntu 22.04                  | PASS               |
+-------------------------------+--------------------+
| CentOS Stream 9               | PASS               |
+-------------------------------+--------------------+
| CentOS Stream 10              | PASS               |
+-------------------------------+--------------------+
| Fedora Linux 43               | PASS               |
+-------------------------------+--------------------+

==== 20 line log output for Ubuntu 24.04 (dpdk_meson_compile): ====
Build machine cpu family: x86_64
Build machine cpu: x86_64
Host machine cpu family: aarch32
Host machine cpu: armv8-a
Target machine cpu family: aarch32
Target machine cpu: armv8-a
Message: ## Building in Developer Mode ##
Program pkg-config found: YES (/usr/bin/pkg-config)
Program check-symbols.sh found: YES (/root/workspace/Generic-DPDK-Compile-Meson/dpdk/buildtools/check-symbols.sh)
Program options-ibverbs-static.sh found: YES (/root/workspace/Generic-DPDK-Compile-Meson/dpdk/buildtools/options-ibverbs-static.sh)
Program python3 found: YES (/usr/bin/python3)
Program python3 (elftools) found: YES (/usr/bin/python3) modules: elftools
Message: Minimum Meson required version is 0.57.2
Program cat found: YES (/usr/bin/cat)
Program ../buildtools/symlink-drivers-solibs.sh found: YES (/bin/sh /root/workspace/Generic-DPDK-Compile-Meson/dpdk/config/../buildtools/symlink-drivers-solibs.sh)
Compiler for C supports arguments -march=armv8-a: NO

config/meson.build:189:8: ERROR: Problem encountered: Compiler does not support "armv8-a" arch flag.

A full log can be found at /root/workspace/Generic-DPDK-Compile-Meson/dpdk/build/meson-logs/meson-log.txt
==== End log output ====

Red Hat Enterprise Linux 9.7
	Kernel: 5.4
	Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-11)

Red Hat Enterprise Linux 10.1
	Kernel: 5.4
	Compiler: gcc gcc (GCC) 14.3.1 20250617 (Red Hat 14.3.1-2)

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

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

Fedora Linux 42
	Kernel: 5.4
	Compiler: gcc gcc (GCC) 15.2.1 20251111 (Red Hat 15.2.1-4)

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

CentOS Stream 9
	Kernel: 5.4
	Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-14)

CentOS Stream 10
	Kernel: 5.4
	Compiler: gcc gcc (GCC) 14.3.1 20251022 (Red Hat 14.3.1-4)

Fedora Linux 43
	Kernel: 5.4
	Compiler: gcc gcc (GCC) 15.2.1 20251211 (Red Hat 15.2.1-5)

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2026-01-12  3:54 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260108081232.5420-1-shperetz@nvidia.com>
2026-01-08  9:01 ` |SUCCESS| " qemudev
2026-01-08  9:06 ` qemudev
2026-01-08  9:44 ` 0-day Robot
2026-01-08  9:45 ` 0-day Robot
2026-01-08 14:30 ` dpdklab
2026-01-08 14:54 ` dpdklab
2026-01-08 15:01 ` dpdklab
2026-01-08 15:02 ` dpdklab
2026-01-08 15:14 ` dpdklab
2026-01-08 15:14 ` dpdklab
2026-01-08 15:15 ` dpdklab
2026-01-08 15:17 ` dpdklab
2026-01-08 21:30 ` dpdklab
2026-01-08 21:57 ` dpdklab
2026-01-09  0:28 ` dpdklab
2026-01-09  0:35 ` dpdklab
2026-01-09  0:41 ` dpdklab
2026-01-09  0:44 ` dpdklab
2026-01-09  0:44 ` dpdklab
2026-01-09  0:44 ` dpdklab
2026-01-09  0:45 ` dpdklab
2026-01-09  0:47 ` dpdklab
2026-01-09  0:54 ` dpdklab
2026-01-09  4:25 ` dpdklab
2026-01-09  5:23 ` |PENDING| " dpdklab
2026-01-09  9:35 ` dpdklab
2026-01-09 15:25 ` |SUCCESS| " dpdklab
2026-01-09 16:20 ` dpdklab
2026-01-09 23:01 ` |PENDING| " dpdklab
2026-01-10 16:30 ` |SUCCESS| " dpdklab
2026-01-10 19:25 ` dpdklab
2026-01-10 21:14 ` dpdklab
2026-01-10 21:36 ` dpdklab
2026-01-10 22:46 ` dpdklab
2026-01-11 21:29 ` |FAILURE| " dpdklab
2026-01-11 21:35 ` dpdklab
2026-01-11 21:52 ` |SUCCESS| " dpdklab
2026-01-12  3:54 ` |FAILURE| " dpdklab
2026-01-12  3:54 ` dpdklab [this message]
2026-01-12  7:11 ` |SUCCESS| " dpdklab
2026-01-12 14:40 ` dpdklab
2026-01-12 14:49 ` dpdklab
2026-01-12 14:49 ` |FAILURE| " dpdklab
2026-01-12 16:45 ` |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=69647090.050a0220.3393d1.cac2SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=shperetz@nvidia.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).