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| pw125177 [PATCH] net/iavf: fix dev stop return value
Date: Thu, 16 Mar 2023 08:58:16 +0000 (UTC)	[thread overview]
Message-ID: <20230316085816.421B66011D@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

_Functional Testing PASS_

Submitter: Zhichao Zeng <zhichaox.zeng@intel.com>
Date: Thursday, March 16 2023 07:14:49 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:8c9bfcb1553d756eb5392a56ac7813b3865c3ec7

125177 --> 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


Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2


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


Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-137-generic aarch64
Compiler: gcc 9.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-03-16  8:58 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-16  8:58 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-20 19:56 dpdklab
2023-03-20 18:03 dpdklab
2023-03-18  8:51 dpdklab
2023-03-18  8:12 dpdklab
2023-03-16 15:53 dpdklab
2023-03-16 15:02 dpdklab
2023-03-16 11:43 dpdklab
2023-03-16 11:43 dpdklab
2023-03-16 10:49 dpdklab
2023-03-16 10:45 dpdklab
2023-03-16 10:24 dpdklab
2023-03-16  9:25 dpdklab
2023-03-16  8:49 dpdklab
2023-03-16  8:48 dpdklab
2023-03-16  8:46 dpdklab
2023-03-16  8:45 dpdklab
2023-03-16  8:44 dpdklab
2023-03-16  8:41 dpdklab
2023-03-16  8:39 dpdklab
2023-03-16  8:36 dpdklab
2023-03-16  8:36 dpdklab
2023-03-16  8:29 dpdklab
2023-03-16  8:29 dpdklab
2023-03-16  8:26 dpdklab
2023-03-16  8:25 dpdklab
2023-03-16  8:25 dpdklab
2023-03-16  8:21 dpdklab
2023-03-16  8:20 dpdklab
2023-03-16  8:19 dpdklab
2023-03-16  8:16 dpdklab
2023-03-16  8:15 dpdklab
2023-03-16  8:09 dpdklab
2023-03-16  8:08 dpdklab
2023-03-16  8:05 dpdklab
2023-03-16  8:03 dpdklab
     [not found] <20230316071449.532296-1-zhichaox.zeng@intel.com>
2023-03-16  6:59 ` qemudev
2023-03-16  7:03 ` qemudev
2023-03-16  7:11 ` checkpatch
2023-03-16  8:59 ` 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=20230316085816.421B66011D@dpdk-ubuntu.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).