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| pw154540 [PATCH] app/testpmd: cross NUMA support
Date: Tue, 17 Jun 2025 11:15:54 -0700 (PDT)	[thread overview]
Message-ID: <6851b0da.250a0220.177a67.24b2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250617155351.190622-1-mkashani@nvidia.com>

Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/154540

_Functional Testing PASS_

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

154540 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#231410

Test environment and result as below:

Ubuntu 24.04
Kernel: 6.8
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
NIC: Intel Corporation 4xxx Series QAT 0 Mbps

Aggregate Results by Test Suite
+----------------------------+--------+
|         Test Suite         | Result |
+============================+========+
| crypto_perf_cryptodev_perf |  PASS  |
+----------------------------+--------+


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

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-17 18:15 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250617155351.190622-1-mkashani@nvidia.com>
2025-06-17 15:23 ` qemudev
2025-06-17 15:27 ` qemudev
2025-06-17 15:55 ` checkpatch
2025-06-17 17:08 ` 0-day Robot
2025-06-17 17:56 ` dpdklab
2025-06-17 18:15 ` dpdklab [this message]
2025-06-17 18:24 ` dpdklab
2025-06-17 18:37 ` dpdklab
2025-06-17 19:13 ` dpdklab
2025-06-17 19:27 ` |PENDING| " dpdklab
2025-06-17 19:38 ` |SUCCESS| " dpdklab
2025-06-17 19:42 ` |FAILURE| " dpdklab
2025-06-17 19:57 ` dpdklab
2025-06-17 20:25 ` |PENDING| " dpdklab
2025-06-17 20:50 ` |SUCCESS| " dpdklab
2025-06-17 21:08 ` dpdklab
2025-06-17 21:20 ` |FAILURE| " dpdklab
2025-06-17 21:35 ` |SUCCESS| " dpdklab
2025-06-17 21:43 ` dpdklab
2025-06-17 21:44 ` dpdklab
2025-06-17 21:46 ` dpdklab
2025-06-17 21:48 ` dpdklab
2025-06-17 21:48 ` dpdklab
2025-06-17 21:49 ` dpdklab
2025-06-17 21:50 ` dpdklab
2025-06-18  0:04 ` |PENDING| " dpdklab
2025-06-18  0:44 ` |FAILURE| " 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=6851b0da.250a0220.177a67.24b2SMTPIN_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).