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: |SUCCESS| pw154537-154539 [PATCH] [3/3] app/testpmd: cross NUMA supp
Date: Wed, 18 Jun 2025 01:01:48 -0700 (PDT)	[thread overview]
Message-ID: <6852726c.050a0220.373ef8.0eb1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250617154255.190093-3-mkashani@nvidia.com>

Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/154539

_Testing PASS_

Submitter: Maayan Kashani <mkashani@nvidia.com>
Date: Tuesday, June 17 2025 15:42:54 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:62a35bbb247e608e235a04ff2941488bc1a78941

154537-154539 --> testing pass

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

Test environment and result as below:

+------------------------------+--------------------+
|         Environment          | dpdk_meson_compile |
+==============================+====================+
| Red Hat Enterprise Linux 9.5 | PASS               |
+------------------------------+--------------------+
| Ubuntu 20.04                 | PASS               |
+------------------------------+--------------------+
| Debian GNU/Linux 12          | PASS               |
+------------------------------+--------------------+
| Fedora 40 (ARM)              | PASS               |
+------------------------------+--------------------+
| Fedora 40 (ARM Clang)        | PASS               |
+------------------------------+--------------------+
| Fedora 41 (ARM)              | PASS               |
+------------------------------+--------------------+
| Fedora Linux 41              | PASS               |
+------------------------------+--------------------+
| Ubuntu 22.04                 | PASS               |
+------------------------------+--------------------+
| Ubuntu 24.04                 | PASS               |
+------------------------------+--------------------+
| CentOS Stream 9 (ARM)        | PASS               |
+------------------------------+--------------------+
| CentOS Stream 10 (ARM)       | PASS               |
+------------------------------+--------------------+


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

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

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

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

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

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

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

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

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

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

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

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

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-18  8:01 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250617154255.190093-3-mkashani@nvidia.com>
2025-06-17 15:09 ` |SUCCESS| pw154537-154539 [PATCH 3/3] app/testpmd: cross NUMA support for gro init qemudev
2025-06-17 15:14 ` qemudev
2025-06-17 15:43 ` |SUCCESS| pw154539 " checkpatch
2025-06-17 17:07 ` |FAILURE| " 0-day Robot
2025-06-17 18:36 ` |SUCCESS| pw154537-154539 [PATCH] [3/3] app/testpmd: cross NUMA supp dpdklab
2025-06-17 18:47 ` dpdklab
2025-06-17 18:57 ` dpdklab
2025-06-17 19:06 ` dpdklab
2025-06-17 19:06 ` dpdklab
2025-06-17 19:07 ` dpdklab
2025-06-17 19:24 ` dpdklab
2025-06-17 19:33 ` dpdklab
2025-06-17 19:41 ` dpdklab
2025-06-17 19:56 ` dpdklab
2025-06-17 20:11 ` |PENDING| " dpdklab
2025-06-17 20:12 ` dpdklab
2025-06-17 20:15 ` |FAILURE| " dpdklab
2025-06-17 20:26 ` |SUCCESS| " dpdklab
2025-06-17 20:34 ` |FAILURE| " dpdklab
2025-06-17 20:53 ` |PENDING| " dpdklab
2025-06-17 21:14 ` |SUCCESS| " dpdklab
2025-06-17 21:17 ` dpdklab
2025-06-17 21:22 ` |PENDING| " dpdklab
2025-06-17 21:30 ` |FAILURE| " dpdklab
2025-06-17 21:32 ` dpdklab
2025-06-17 21:46 ` |SUCCESS| " dpdklab
2025-06-17 21:47 ` dpdklab
2025-06-17 22:04 ` dpdklab
2025-06-17 22:16 ` |FAILURE| " dpdklab
2025-06-17 22:18 ` |SUCCESS| " dpdklab
2025-06-17 22:27 ` |FAILURE| " dpdklab
2025-06-17 22:27 ` dpdklab
2025-06-17 22:28 ` dpdklab
2025-06-17 22:37 ` |SUCCESS| " dpdklab
2025-06-18  0:48 ` |PENDING| " dpdklab
2025-06-18  1:21 ` |FAILURE| " dpdklab
2025-06-18  2:08 ` dpdklab
2025-06-18  3:37 ` |SUCCESS| " dpdklab
2025-06-18  4:08 ` dpdklab
2025-06-18  4:19 ` dpdklab
2025-06-18  5:21 ` dpdklab
2025-06-18  7:54 ` dpdklab
2025-06-18  7:57 ` dpdklab
2025-06-18  8:01 ` dpdklab [this message]
2025-06-18  8:06 ` dpdklab
2025-06-18  8:09 ` 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=6852726c.050a0220.373ef8.0eb1SMTPIN_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).