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| pw143937 [PATCH] [v4,1/1] testpmd: add hairpin-map paramet
Date: Wed, 11 Sep 2024 13:41:50 -0700 (PDT)	[thread overview]
Message-ID: <66e2008e.050a0220.297a8f.d6f4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240911050833.202698-1-getelson@nvidia.com>

Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/143937

_Functional Testing PASS_

Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Wednesday, September 11 2024 05:08:33 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:523fd7b3adfdf5a87651e8ca33bc69223b3211d5

143937 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#179935

Test environment and result as below:

Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps

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


Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps

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


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-09-11 20:41 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240911050833.202698-1-getelson@nvidia.com>
2024-09-11  4:42 ` |SUCCESS| pw143937 [PATCH v4 1/1] testpmd: add hairpin-map parameter qemudev
2024-09-11  4:47 ` qemudev
2024-09-11  5:11 ` |WARNING| " checkpatch
2024-09-11  6:04 ` |FAILURE| " 0-day Robot
2024-09-11 12:04 ` |SUCCESS| pw143937 [PATCH] [v4,1/1] testpmd: add hairpin-map paramet dpdklab
2024-09-11 12:11 ` dpdklab
2024-09-11 12:16 ` dpdklab
2024-09-11 12:18 ` dpdklab
2024-09-11 12:25 ` dpdklab
2024-09-11 12:39 ` |PENDING| " dpdklab
2024-09-11 12:43 ` |SUCCESS| " dpdklab
2024-09-11 12:43 ` dpdklab
2024-09-11 12:45 ` dpdklab
2024-09-11 12:58 ` |PENDING| " dpdklab
2024-09-11 12:59 ` |SUCCESS| " dpdklab
2024-09-11 13:07 ` dpdklab
2024-09-11 13:08 ` dpdklab
2024-09-11 13:19 ` |PENDING| " dpdklab
2024-09-11 13:19 ` dpdklab
2024-09-11 13:20 ` |SUCCESS| " dpdklab
2024-09-11 13:31 ` |PENDING| " dpdklab
2024-09-11 13:48 ` dpdklab
2024-09-11 16:16 ` |SUCCESS| " dpdklab
2024-09-11 16:16 ` dpdklab
2024-09-11 16:46 ` dpdklab
2024-09-11 19:06 ` dpdklab
2024-09-11 19:47 ` dpdklab
2024-09-11 19:51 ` |PENDING| " dpdklab
2024-09-11 19:52 ` |SUCCESS| " dpdklab
2024-09-11 19:57 ` dpdklab
2024-09-11 19:57 ` dpdklab
2024-09-11 20:18 ` dpdklab
2024-09-11 20:19 ` dpdklab
2024-09-11 20:26 ` dpdklab
2024-09-11 20:28 ` |PENDING| " dpdklab
2024-09-11 20:32 ` |SUCCESS| " dpdklab
2024-09-11 20:33 ` dpdklab
2024-09-11 20:36 ` dpdklab
2024-09-11 20:41 ` dpdklab [this message]
2024-09-11 20:50 ` dpdklab
2024-09-11 20:50 ` dpdklab
2024-09-11 21:02 ` dpdklab
2024-09-11 21:06 ` dpdklab
2024-09-11 21:10 ` dpdklab
2024-09-11 21:57 ` dpdklab
2024-09-11 22:04 ` |FAILURE| " dpdklab
2024-09-11 22:17 ` |SUCCESS| " dpdklab
2024-09-11 22:17 ` dpdklab
2024-09-11 22:30 ` |FAILURE| " dpdklab
2024-09-11 23:03 ` dpdklab
2024-09-12  2:16 ` |SUCCESS| " dpdklab
2024-09-12  3:42 ` dpdklab
2024-09-15 15:58 ` dpdklab
2024-09-15 17:01 ` dpdklab
2024-09-15 21:47 ` dpdklab
2024-09-15 22:16 ` 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=66e2008e.050a0220.297a8f.d6f4SMTPIN_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).