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| pw137199 [PATCH] net/virtio-user: support IOVA as PA mode
Date: Mon, 26 Feb 2024 04:50:31 -0800 (PST)	[thread overview]
Message-ID: <65dc8917.050a0220.e54bf.4c80SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Srujana Challa <schalla@marvell.com>
Date: Monday, February 26 2024 11:40:19 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2176806a4052a28bce70fe1767d8a56c6d7e904e

137199 --> 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/3


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


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-26 12:50 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26 12:50 dpdklab [this message]
     [not found] <20240226114019.2127838-1-schalla@marvell.com>
2024-02-28  0:45 ` dpdklab
2024-02-28  1:00 ` dpdklab
2024-02-28  1:00 ` dpdklab
2024-02-28  1:28 ` dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2024-02-26 16:06 dpdklab
2024-02-26 15:38 dpdklab
2024-02-26 15:15 dpdklab
2024-02-26 14:09 dpdklab
2024-02-26 14:02 dpdklab
2024-02-26 13:47 dpdklab
2024-02-26 13:34 dpdklab
2024-02-26 13:27 dpdklab
2024-02-26 13:26 dpdklab
2024-02-26 13:26 dpdklab
2024-02-26 13:23 dpdklab
2024-02-26 13:22 dpdklab
2024-02-26 13:21 dpdklab
2024-02-26 13:19 dpdklab
2024-02-26 13:17 dpdklab
2024-02-26 13:16 dpdklab
2024-02-26 13:16 dpdklab
2024-02-26 13:16 dpdklab
2024-02-26 13:16 dpdklab
2024-02-26 13:15 dpdklab
2024-02-26 13:14 dpdklab
2024-02-26 13:14 dpdklab
2024-02-26 13:14 dpdklab
2024-02-26 13:13 dpdklab
2024-02-26 13:13 dpdklab
2024-02-26 13:13 dpdklab
2024-02-26 13:01 dpdklab
2024-02-26 13:01 dpdklab
2024-02-26 13:00 dpdklab
2024-02-26 13:00 dpdklab
2024-02-26 12:59 dpdklab
2024-02-26 12:59 dpdklab
2024-02-26 12:59 dpdklab
2024-02-26 12:59 dpdklab
2024-02-26 12:59 dpdklab
2024-02-26 12:58 dpdklab
2024-02-26 12:58 dpdklab
2024-02-26 12:57 dpdklab
2024-02-26 12:57 dpdklab
2024-02-26 12:56 dpdklab
2024-02-26 12:56 dpdklab
2024-02-26 12:55 dpdklab
2024-02-26 12:55 dpdklab
2024-02-26 12:54 dpdklab
2024-02-26 12:54 dpdklab
2024-02-26 12:54 dpdklab
2024-02-26 12:53 dpdklab
2024-02-26 12:53 dpdklab
2024-02-26 12:53 dpdklab
2024-02-26 12:53 dpdklab
2024-02-26 12:52 dpdklab
2024-02-26 12:52 dpdklab
2024-02-26 12:52 dpdklab
2024-02-26 12:51 dpdklab
2024-02-26 12:51 dpdklab
2024-02-26 12:51 dpdklab
2024-02-26 12:50 dpdklab
2024-02-26 12:50 dpdklab
2024-02-26 12:49 dpdklab
2024-02-26 12:49 dpdklab
2024-02-26 12:48 dpdklab
2024-02-26 12:45 dpdklab
2024-02-26 12:44 dpdklab
2024-02-26 12:43 dpdklab
2024-02-26 12:34 dpdklab
2024-02-26 12:33 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=65dc8917.050a0220.e54bf.4c80SMTPIN_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).