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| pw131100-131129 [PATCH] [v5,32/32] net/sssnic: add VF dev
Date: Sun, 03 Sep 2023 22:42:41 -0700 (PDT)	[thread overview]
Message-ID: <64f56e51.0c0a0220.15052.a0c4SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Renyong Wan <wanry@3snic.com>
Date: Monday, September 04 2023 04:56:58 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:799d56f1192d72872e63fbb3d2c7f776b7ae89b0

131100-131129 --> functional testing pass

Test environment and result as below:

Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-09-04  5:42 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-04  5:42 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-06  4:24 dpdklab
2023-09-06  4:01 dpdklab
2023-09-06  3:58 dpdklab
2023-09-06  3:55 dpdklab
2023-09-05 14:32 dpdklab
2023-09-04  7:04 dpdklab
2023-09-04  6:12 dpdklab
2023-09-04  6:07 dpdklab
2023-09-04  6:02 dpdklab
2023-09-04  6:01 dpdklab
2023-09-04  6:01 dpdklab
2023-09-04  6:01 dpdklab
2023-09-04  5:59 dpdklab
2023-09-04  5:59 dpdklab
2023-09-04  5:59 dpdklab
2023-09-04  5:58 dpdklab
2023-09-04  5:57 dpdklab
2023-09-04  5:57 dpdklab
2023-09-04  5:56 dpdklab
2023-09-04  5:56 dpdklab
2023-09-04  5:55 dpdklab
2023-09-04  5:54 dpdklab
2023-09-04  5:53 dpdklab
2023-09-04  5:53 dpdklab
2023-09-04  5:53 dpdklab
2023-09-04  5:52 dpdklab
2023-09-04  5:51 dpdklab
2023-09-04  5:51 dpdklab
2023-09-04  5:48 dpdklab
2023-09-04  5:48 dpdklab
2023-09-04  5:47 dpdklab
2023-09-04  5:47 dpdklab
2023-09-04  5:47 dpdklab
2023-09-04  5:47 dpdklab
2023-09-04  5:46 dpdklab
2023-09-04  5:46 dpdklab
2023-09-04  5:45 dpdklab
2023-09-04  5:45 dpdklab
2023-09-04  5:44 dpdklab
2023-09-04  5:44 dpdklab
2023-09-04  5:44 dpdklab
2023-09-04  5:44 dpdklab
2023-09-04  5:43 dpdklab
2023-09-04  5:43 dpdklab
2023-09-04  5:42 dpdklab
2023-09-04  5:42 dpdklab
2023-09-04  5:42 dpdklab
2023-09-04  5:41 dpdklab
2023-09-04  5:41 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=64f56e51.0c0a0220.15052.a0c4SMTPIN_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).