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| pw134103 [PATCH] net/iavf: fix error devargs parsing
Date: Fri, 10 Nov 2023 07:19:14 -0800 (PST)	[thread overview]
Message-ID: <654e49f2.b00a0220.508a8.d2aeSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Friday, November 10 2023 10:20:15 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:de0ec3c2458e3e2ce53e504c4ba92a36fcc78ef3

134103 --> functional testing pass

Test environment and result as below:

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


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


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-11-10 15:19 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-10 15:19 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-14 18:29 dpdklab
2023-11-14 18:11 dpdklab
2023-11-10 22:44 dpdklab
2023-11-10 19:10 dpdklab
2023-11-10 18:14 dpdklab
2023-11-10 17:33 dpdklab
2023-11-10 16:54 dpdklab
2023-11-10 16:53 dpdklab
2023-11-10 16:52 dpdklab
2023-11-10 16:52 dpdklab
2023-11-10 16:52 dpdklab
2023-11-10 16:51 dpdklab
2023-11-10 16:51 dpdklab
2023-11-10 16:51 dpdklab
2023-11-10 16:50 dpdklab
2023-11-10 16:50 dpdklab
2023-11-10 16:50 dpdklab
2023-11-10 16:47 dpdklab
2023-11-10 16:47 dpdklab
2023-11-10 16:46 dpdklab
2023-11-10 16:46 dpdklab
2023-11-10 16:46 dpdklab
2023-11-10 16:45 dpdklab
2023-11-10 16:45 dpdklab
2023-11-10 16:45 dpdklab
2023-11-10 16:45 dpdklab
2023-11-10 16:44 dpdklab
2023-11-10 16:44 dpdklab
2023-11-10 16:43 dpdklab
2023-11-10 16:43 dpdklab
2023-11-10 16:38 dpdklab
2023-11-10 16:38 dpdklab
2023-11-10 16:30 dpdklab
2023-11-10 16:30 dpdklab
2023-11-10 16:30 dpdklab
2023-11-10 16:30 dpdklab
2023-11-10 16:30 dpdklab
2023-11-10 16:29 dpdklab
2023-11-10 16:29 dpdklab
2023-11-10 16:29 dpdklab
2023-11-10 16:29 dpdklab
2023-11-10 16:29 dpdklab
2023-11-10 16:28 dpdklab
2023-11-10 16:28 dpdklab
2023-11-10 16:28 dpdklab
2023-11-10 15:47 dpdklab
2023-11-10 15:37 dpdklab
2023-11-10 15:21 dpdklab
2023-11-10 15:19 dpdklab
2023-11-10 15:16 dpdklab
2023-11-10 15:16 dpdklab
2023-11-10 15:15 dpdklab
2023-11-10 15:12 dpdklab
2023-11-10 14:58 dpdklab
     [not found] <20231110102015.469031-1-mingjinx.ye@intel.com>
2023-11-10 10:12 ` qemudev
2023-11-10 10:16 ` qemudev
2023-11-10 10:32 ` checkpatch
2023-11-10 11:39 ` 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=654e49f2.b00a0220.508a8.d2aeSMTPIN_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).