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| pw131014-131041 [PATCH] [v3,32/32] net/sssnic: add VF dev
Date: Tue, 05 Sep 2023 22:33:59 -0700 (PDT)	[thread overview]
Message-ID: <64f80f47.250a0220.f5a2f.42d8SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Renyong Wan <wanry@3snic.com>
Date: Friday, September 01 2023 03:28:42 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:62774b78a84e9fa5df56d04cffed69bef8c901f1

131014-131041 --> functional testing pass

Test environment and result as below:

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


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


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-09-06  5:34 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-06  5:33 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-06  5:56 dpdklab
2023-09-06  5:44 dpdklab
2023-09-06  5:39 dpdklab
2023-09-01 10:11 dpdklab
2023-09-01  9:49 dpdklab
2023-09-01  9:44 dpdklab
2023-09-01  9:42 dpdklab
2023-09-01  9:40 dpdklab
2023-09-01  9:29 dpdklab
2023-09-01  8:59 dpdklab
2023-09-01  8:58 dpdklab
2023-09-01  8:57 dpdklab
2023-09-01  8:55 dpdklab
2023-09-01  8:49 dpdklab
2023-09-01  8:48 dpdklab
2023-09-01  8:45 dpdklab
2023-09-01  8:43 dpdklab
2023-09-01  8:42 dpdklab
2023-09-01  8:41 dpdklab
2023-09-01  8:39 dpdklab
2023-09-01  8:39 dpdklab
2023-09-01  8:38 dpdklab
2023-09-01  8:35 dpdklab
2023-09-01  8:34 dpdklab
2023-09-01  8:34 dpdklab
2023-09-01  8:33 dpdklab
2023-09-01  8:33 dpdklab
2023-09-01  8:32 dpdklab
2023-09-01  8:32 dpdklab
2023-09-01  8:32 dpdklab
2023-09-01  8:31 dpdklab
2023-09-01  8:30 dpdklab
2023-09-01  8:30 dpdklab
2023-09-01  8:29 dpdklab
2023-09-01  8:29 dpdklab
2023-09-01  8:29 dpdklab
2023-09-01  8:28 dpdklab
2023-09-01  8:28 dpdklab
2023-09-01  8:28 dpdklab
2023-09-01  8:27 dpdklab
2023-09-01  8:27 dpdklab
2023-09-01  8:27 dpdklab
2023-09-01  8:27 dpdklab
2023-09-01  8:27 dpdklab
2023-09-01  8:27 dpdklab
2023-09-01  8:25 dpdklab
2023-09-01  8:25 dpdklab
2023-09-01  8:25 dpdklab
2023-09-01  8:25 dpdklab
2023-09-01  8:25 dpdklab
2023-09-01  8:25 dpdklab
2023-09-01  8:24 dpdklab
2023-09-01  8:24 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=64f80f47.250a0220.f5a2f.42d8SMTPIN_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).