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, Xueming Li <xuemingl@nvidia.com>,
	Christian Ehrhardt <christian.ehrhardt@canonical.com>,
	Kevin Traynor <ktraynor@redhat.com>,
	Luca Boccassi <bluca@debian.org>
Subject: |SUCCESS| [GIT MASTER] 65491527fa667ee05abf48043978ace2e6cbb154
Date: Fri, 29 Nov 2024 22:35:40 -0800 (PST)	[thread overview]
Message-ID: <674ab23c.050a0220.358b7d.ca8fSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Functional Testing PASS_

Branch: tags/v22.11

65491527fa667ee05abf48043978ace2e6cbb154 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#200208

Test environment and result as below:

Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps

Aggregate Results by Test Suite
+-----------------------------+--------+
|         Test Suite          | Result |
+=============================+========+
| unit_tests_mbuf             |  PASS  |
+-----------------------------+--------+
| vhost_virtio_user_interrupt |  PASS  |
+-----------------------------+--------+
| virtio_smoke                |  PASS  |
+-----------------------------+--------+


Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps

Aggregate Results by Test Suite
+-----------------------------+--------+
|         Test Suite          | Result |
+=============================+========+
| unit_tests_mbuf             |  PASS  |
+-----------------------------+--------+
| vhost_virtio_user_interrupt |  PASS  |
+-----------------------------+--------+
| virtio_smoke                |  PASS  |
+-----------------------------+--------+


To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/31789/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-11-30  6:35 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-30  6:35 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-30  9:10 dpdklab
2024-11-30  8:32 dpdklab
2024-11-30  8:10 dpdklab
2024-11-30  8:00 dpdklab
2024-11-30  7:47 dpdklab
2024-11-30  7:20 dpdklab
2024-11-30  7:10 dpdklab
2024-11-30  6:38 dpdklab
2024-11-30  6:26 dpdklab
2024-11-30  6:02 dpdklab
2024-11-30  6:01 dpdklab
2024-11-30  5:36 dpdklab
2024-11-28 14:32 dpdklab
2024-11-28  7:59 dpdklab
2024-11-28  7:37 dpdklab
2024-11-28  7:25 dpdklab
2024-11-28  7:24 dpdklab
2024-11-28  7:04 dpdklab
2024-11-28  6:22 dpdklab
2024-11-28  6:06 dpdklab
2024-11-28  6:00 dpdklab
2024-11-28  5:38 dpdklab
2024-11-27  8:10 dpdklab
2024-11-27  7:46 dpdklab
2024-11-27  7:42 dpdklab
2024-11-27  7:40 dpdklab
2024-11-27  7:32 dpdklab
2024-11-27  7:30 dpdklab
2024-11-27  7:14 dpdklab
2024-11-27  7:11 dpdklab
2024-11-27  7:10 dpdklab
2024-11-27  6:37 dpdklab
2024-11-27  6:28 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=674ab23c.050a0220.358b7d.ca8fSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ktraynor@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=xuemingl@nvidia.com \
    /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).