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| pw132146 [PATCH] [v3] testpmd: add hairpin-map parameter
Date: Thu, 28 Sep 2023 17:23:20 -0700 (PDT)	[thread overview]
Message-ID: <651618f8.0d0a0220.340a1.ce43SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Thursday, September 28 2023 15:36:05 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:c56185fc183fc0532d2f03aaf04bbf0989ea91a5

132146 --> functional testing pass

Test environment and result as below:

Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


Ubuntu 22.04
Kernel: 5.15.0-58-generic x86_64
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2


Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 9.4
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-09-29  0:23 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-29  0:23 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-29  4:40 dpdklab
2023-09-29  1:33 dpdklab
2023-09-29  1:32 dpdklab
2023-09-29  1:28 dpdklab
2023-09-29  1:27 dpdklab
2023-09-29  1:27 dpdklab
2023-09-29  1:26 dpdklab
2023-09-29  1:24 dpdklab
2023-09-29  1:04 dpdklab
2023-09-29  1:03 dpdklab
2023-09-29  1:03 dpdklab
2023-09-29  0:58 dpdklab
2023-09-29  0:57 dpdklab
2023-09-29  0:54 dpdklab
2023-09-29  0:54 dpdklab
2023-09-29  0:48 dpdklab
2023-09-29  0:47 dpdklab
2023-09-29  0:46 dpdklab
2023-09-29  0:44 dpdklab
2023-09-29  0:41 dpdklab
2023-09-29  0:40 dpdklab
2023-09-29  0:36 dpdklab
2023-09-29  0:31 dpdklab
2023-09-29  0:30 dpdklab
2023-09-29  0:28 dpdklab
2023-09-29  0:28 dpdklab
2023-09-29  0:27 dpdklab
2023-09-29  0:27 dpdklab
2023-09-29  0:27 dpdklab
2023-09-29  0:27 dpdklab
2023-09-29  0:26 dpdklab
2023-09-29  0:26 dpdklab
2023-09-29  0:26 dpdklab
2023-09-29  0:26 dpdklab
2023-09-29  0:26 dpdklab
2023-09-29  0:26 dpdklab
2023-09-29  0:25 dpdklab
2023-09-29  0:25 dpdklab
2023-09-29  0:25 dpdklab
2023-09-29  0:24 dpdklab
2023-09-29  0:23 dpdklab
2023-09-29  0:16 dpdklab
2023-09-29  0:00 dpdklab
2023-09-29  0:00 dpdklab
2023-09-28 23:59 dpdklab
2023-09-28 23:59 dpdklab
2023-09-28 23:58 dpdklab
2023-09-28 23:55 dpdklab
2023-09-28 23:55 dpdklab
     [not found] <20230928153605.759397-1-getelson@nvidia.com>
2023-09-28 15:17 ` |SUCCESS| pw132146 [PATCH v3] " qemudev
2023-09-28 15:21 ` qemudev
2023-09-28 16:39 ` 0-day Robot

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=651618f8.0d0a0220.340a1.ce43SMTPIN_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).