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| pw130261 [PATCH] doc: add note about VMXNET3 on AMD with E
Date: Mon, 14 Aug 2023 09:49:18 -0700 (PDT)	[thread overview]
Message-ID: <64da5b0e.630a0220.87fa6.4265SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Igor de Paula <igordptx@gmail.com>
Date: Monday, August 14 2023 11:31:04 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:68150b90bda5e8f81ad1b1bad82be653b1d42a81

130261 --> 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 XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4


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


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-08-14 16:49 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-14 16:49 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-14 21:36 dpdklab
2023-08-14 21:19 dpdklab
2023-08-14 21:15 dpdklab
2023-08-14 21:04 dpdklab
2023-08-14 20:59 dpdklab
2023-08-14 17:39 dpdklab
2023-08-14 17:28 dpdklab
2023-08-14 17:17 dpdklab
2023-08-14 16:53 dpdklab
2023-08-14 16:52 dpdklab
2023-08-14 16:51 dpdklab
2023-08-14 16:50 dpdklab
2023-08-14 16:49 dpdklab
2023-08-14 16:49 dpdklab
2023-08-14 16:47 dpdklab
2023-08-14 16:46 dpdklab
2023-08-14 16:45 dpdklab
2023-08-14 16:45 dpdklab
2023-08-14 16:44 dpdklab
2023-08-14 16:43 dpdklab
2023-08-14 16:41 dpdklab
2023-08-14 16:34 dpdklab
2023-08-14 16:34 dpdklab
2023-08-14 16:24 dpdklab
2023-08-14 16:24 dpdklab
2023-08-14 16:23 dpdklab
2023-08-14 16:22 dpdklab
2023-08-14 16:22 dpdklab
2023-08-14 16:22 dpdklab
2023-08-14 16:22 dpdklab
2023-08-14 16:21 dpdklab
2023-08-14 16:21 dpdklab
2023-08-14 16:19 dpdklab
2023-08-14 16:19 dpdklab
2023-08-14 16:19 dpdklab
2023-08-14 16:19 dpdklab
2023-08-14 16:19 dpdklab
2023-08-14 16:19 dpdklab
2023-08-14 16:19 dpdklab
2023-08-14 16:19 dpdklab
2023-08-14 16:18 dpdklab
2023-08-14 16:17 dpdklab
2023-08-14 16:17 dpdklab
2023-08-14 16:17 dpdklab
2023-08-14 16:16 dpdklab
2023-08-14 16:16 dpdklab
2023-08-14 16:16 dpdklab
2023-08-14 16:16 dpdklab
2023-08-14 16:15 dpdklab
2023-08-14 16:15 dpdklab
2023-08-14 16:15 dpdklab
2023-08-14 16:15 dpdklab
2023-08-14 16:14 dpdklab
2023-08-14 16:14 dpdklab
2023-08-14 16:07 dpdklab
2023-08-14 16:06 dpdklab
2023-08-14 16:04 dpdklab
2023-08-14 15:51 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=64da5b0e.630a0220.87fa6.4265SMTPIN_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).