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,
	David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw124075-124078 [PATCH] [v2, 4/4] doc: update supported devices for NVIDIA NICs
Date: Thu, 16 Feb 2023 09:28:56 -0500 (EST)	[thread overview]
Message-ID: <20230216142856.D58FB10619A@noxus.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 842 bytes --]

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

_Functional Testing PASS_

Submitter: Raslan Darawsheh <rasland@nvidia.com>
Date: Thursday, February 16 2023 14:04:14 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:01314192b7856d3737eb6d80aa351f60a07631af

124075-124078 --> functional testing pass

Test environment and result as below:

Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-137-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/2


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-02-16 14:28 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16 14:28 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-02-24 23:11 dpdklab
2023-02-19 10:54 dpdklab
2023-02-17 23:51 dpdklab
2023-02-16 18:31 dpdklab
2023-02-16 18:31 dpdklab
2023-02-16 18:30 dpdklab
2023-02-16 18:25 dpdklab
2023-02-16 18:22 dpdklab
2023-02-16 18:21 dpdklab
2023-02-16 18:13 dpdklab
2023-02-16 18:11 dpdklab
2023-02-16 18:07 dpdklab
2023-02-16 17:58 dpdklab
2023-02-16 17:51 dpdklab
2023-02-16 17:43 dpdklab
2023-02-16 17:42 dpdklab
2023-02-16 17:32 dpdklab
2023-02-16 14:51 dpdklab
2023-02-16 14:48 dpdklab
2023-02-16 14:45 dpdklab
2023-02-16 14:45 dpdklab
2023-02-16 14:44 dpdklab
2023-02-16 14:41 dpdklab
2023-02-16 14:40 dpdklab
2023-02-16 14:38 dpdklab
2023-02-16 14:32 dpdklab
     [not found] <20230216140415.2730446-5-rasland@nvidia.com>
2023-02-16 14:02 ` |SUCCESS| pw124075-124078 [PATCH v2 " qemudev
2023-02-16 14:06 ` qemudev

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=20230216142856.D58FB10619A@noxus.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).