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| pw138336 [PATCH] net/iavf: fix fail to reset vf when using
Date: Wed, 13 Mar 2024 19:29:12 -0700 (PDT)	[thread overview]
Message-ID: <65f260f8.170a0220.bf0f2.1d6aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240314010049.340381-1-kaiwenx.deng@intel.com>

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

_Functional Testing PASS_

Submitter: Kaiwen Deng <kaiwenx.deng@intel.com>
Date: Thursday, March 14 2024 01:00:49 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:19082c1fac430c74bb4b1c101edd12d88928e7c2

138336 --> functional testing pass

Test environment and result as below:

Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-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


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/29540/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-14  2:29 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240314010049.340381-1-kaiwenx.deng@intel.com>
2024-03-14  1:27 ` |SUCCESS| pw138336 [PATCH] net/iavf: fix fail to reset vf when using dcf qemudev
2024-03-14  1:31 ` qemudev
2024-03-14  1:45 ` checkpatch
2024-03-14  2:19 ` |SUCCESS| pw138336 [PATCH] net/iavf: fix fail to reset vf when using dpdklab
2024-03-14  2:20 ` dpdklab
2024-03-14  2:20 ` dpdklab
2024-03-14  2:21 ` dpdklab
2024-03-14  2:23 ` dpdklab
2024-03-14  2:23 ` dpdklab
2024-03-14  2:24 ` dpdklab
2024-03-14  2:24 ` dpdklab
2024-03-14  2:24 ` dpdklab
2024-03-14  2:24 ` dpdklab
2024-03-14  2:25 ` dpdklab
2024-03-14  2:25 ` dpdklab
2024-03-14  2:25 ` dpdklab
2024-03-14  2:25 ` dpdklab
2024-03-14  2:26 ` dpdklab
2024-03-14  2:26 ` dpdklab
2024-03-14  2:26 ` dpdklab
2024-03-14  2:26 ` dpdklab
2024-03-14  2:27 ` dpdklab
2024-03-14  2:27 ` dpdklab
2024-03-14  2:27 ` dpdklab
2024-03-14  2:27 ` dpdklab
2024-03-14  2:27 ` dpdklab
2024-03-14  2:28 ` dpdklab
2024-03-14  2:28 ` dpdklab
2024-03-14  2:29 ` dpdklab
2024-03-14  2:29 ` dpdklab [this message]
2024-03-14  2:29 ` dpdklab
2024-03-14  2:29 ` dpdklab
2024-03-14  2:29 ` dpdklab
2024-03-14  2:29 ` dpdklab
2024-03-14  2:29 ` dpdklab
2024-03-14  2:29 ` dpdklab
2024-03-14  2:30 ` dpdklab
2024-03-14  2:30 ` dpdklab
2024-03-14  2:30 ` dpdklab
2024-03-14  2:30 ` dpdklab
2024-03-14  2:31 ` dpdklab
2024-03-14  2:34 ` dpdklab
2024-03-14  2:34 ` dpdklab
2024-03-14  2:35 ` dpdklab
2024-03-14  2:35 ` dpdklab
2024-03-14  2:37 ` dpdklab
2024-03-14  2:38 ` dpdklab
2024-03-14  2:38 ` dpdklab
2024-03-14  2:38 ` dpdklab
2024-03-14  2:38 ` dpdklab
2024-03-14  2:38 ` dpdklab
2024-03-14  2:39 ` dpdklab
2024-03-14  2:39 ` dpdklab
2024-03-14  2:39 ` dpdklab
2024-03-14  2:40 ` dpdklab
2024-03-14  2:40 ` dpdklab
2024-03-14  2:41 ` dpdklab
2024-03-14  2:43 ` |SUCCESS| pw138336 [PATCH] net/iavf: fix fail to reset vf when using dcf 0-day Robot
2024-03-14  2:46 ` |SUCCESS| pw138336 [PATCH] net/iavf: fix fail to reset vf when using dpdklab
2024-03-14  2:52 ` dpdklab
2024-03-14  2:53 ` dpdklab
2024-03-14  2:53 ` dpdklab
2024-03-14  2:55 ` dpdklab
2024-03-14  2:55 ` dpdklab
2024-03-14  2:55 ` dpdklab
2024-03-14  2:55 ` dpdklab
2024-03-14  2:56 ` dpdklab
2024-03-14  2:56 ` dpdklab
2024-03-14  2:57 ` dpdklab
2024-03-14  2:58 ` dpdklab
2024-03-14  2:59 ` dpdklab
2024-03-14  3:21 ` dpdklab
2024-03-14  3:42 ` dpdklab
2024-03-17 14:43 ` dpdklab
2024-03-17 15:23 ` 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=65f260f8.170a0220.bf0f2.1d6aSMTPIN_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).