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] 680818068d31764357075cde440232ce5ab8b786
Date: Wed, 11 Sep 2024 22:53:50 -0700 (PDT)	[thread overview]
Message-ID: <66e281ee.050a0220.cbe8.4f23SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Functional Testing PASS_

Branch: tags/v21.11

680818068d31764357075cde440232ce5ab8b786 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#180146

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 82599ES 10000 Mbps

Aggregate Results by Test Suite
+-----------------------------+--------+
|         Test Suite          | Result |
+=============================+========+
| scatter                     |  PASS  |
+-----------------------------+--------+
| 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 XL710-QDA2 40000 Mbps

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


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-09-12  5:53 UTC|newest]

Thread overview: 142+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12  5:53 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-19 19:20 dpdklab
2024-09-19 18:21 dpdklab
2024-09-19 15:33 dpdklab
2024-09-19 15:31 dpdklab
2024-09-19 13:30 dpdklab
2024-09-19 12:12 dpdklab
2024-09-19 12:07 dpdklab
2024-09-19 11:53 dpdklab
2024-09-19 11:48 dpdklab
2024-09-19 11:46 dpdklab
2024-09-19 11:44 dpdklab
2024-09-19 11:03 dpdklab
2024-09-19  9:20 dpdklab
2024-09-19  9:00 dpdklab
2024-09-19  8:58 dpdklab
2024-09-18 11:08 dpdklab
2024-09-18  9:35 dpdklab
2024-09-18  9:10 dpdklab
2024-09-18  9:06 dpdklab
2024-09-18  8:55 dpdklab
2024-09-18  8:10 dpdklab
2024-09-18  6:37 dpdklab
2024-09-18  6:02 dpdklab
2024-09-18  5:26 dpdklab
2024-09-18  2:50 dpdklab
2024-09-18  2:03 dpdklab
2024-09-18  1:07 dpdklab
2024-09-17 21:25 dpdklab
2024-09-17 19:47 dpdklab
2024-09-17 13:42 dpdklab
2024-09-17 13:35 dpdklab
2024-09-17 11:18 dpdklab
2024-09-17 10:18 dpdklab
2024-09-17 10:15 dpdklab
2024-09-17  9:50 dpdklab
2024-09-17  9:36 dpdklab
2024-09-17  8:23 dpdklab
2024-09-17  6:47 dpdklab
2024-09-17  6:37 dpdklab
2024-09-17  6:31 dpdklab
2024-09-17  6:11 dpdklab
2024-09-17  5:45 dpdklab
2024-09-17  2:22 dpdklab
2024-09-16 15:19 dpdklab
2024-09-16 13:07 dpdklab
2024-09-16  7:06 dpdklab
2024-09-16  7:01 dpdklab
2024-09-16  6:49 dpdklab
2024-09-16  6:10 dpdklab
2024-09-16  4:55 dpdklab
2024-09-16  3:42 dpdklab
2024-09-15 19:02 dpdklab
2024-09-15 10:08 dpdklab
2024-09-15  7:17 dpdklab
2024-09-15  7:16 dpdklab
2024-09-15  7:14 dpdklab
2024-09-15  6:54 dpdklab
2024-09-15  6:18 dpdklab
2024-09-15  4:54 dpdklab
2024-09-15  3:56 dpdklab
2024-09-14 23:12 dpdklab
2024-09-14 21:51 dpdklab
2024-09-14 21:41 dpdklab
2024-09-14 10:07 dpdklab
2024-09-14  8:29 dpdklab
2024-09-14  6:10 dpdklab
2024-09-14  5:44 dpdklab
2024-09-14  5:42 dpdklab
2024-09-14  5:33 dpdklab
2024-09-14  5:12 dpdklab
2024-09-14  5:10 dpdklab
2024-09-14  5:07 dpdklab
2024-09-13 10:59 dpdklab
2024-09-13 10:28 dpdklab
2024-09-13  6:40 dpdklab
2024-09-13  6:38 dpdklab
2024-09-13  6:26 dpdklab
2024-09-13  6:12 dpdklab
2024-09-13  5:37 dpdklab
2024-09-13  5:26 dpdklab
2024-09-13  4:52 dpdklab
2024-09-12 14:04 dpdklab
2024-09-12 13:15 dpdklab
2024-09-12 12:42 dpdklab
2024-09-12 12:06 dpdklab
2024-09-12  7:29 dpdklab
2024-09-12  5:39 dpdklab
2024-09-12  5:39 dpdklab
2024-09-11 17:38 dpdklab
2024-09-11 13:53 dpdklab
2024-09-11 11:22 dpdklab
2024-09-11  9:30 dpdklab
2024-09-11  7:19 dpdklab
2024-09-11  7:19 dpdklab
2024-09-11  6:26 dpdklab
2024-09-11  6:21 dpdklab
2024-09-11  5:29 dpdklab
2024-09-10 13:47 dpdklab
2024-09-10 13:46 dpdklab
2024-09-10 12:42 dpdklab
2024-09-10 12:40 dpdklab
2024-09-10  9:29 dpdklab
2024-09-10  9:22 dpdklab
2024-09-10  6:04 dpdklab
2024-09-10  5:26 dpdklab
2024-09-10  4:59 dpdklab
2024-09-10  4:56 dpdklab
2024-09-09  8:55 dpdklab
2024-09-09  8:50 dpdklab
2024-09-09  7:53 dpdklab
2024-09-09  7:53 dpdklab
2024-09-09  6:46 dpdklab
2024-09-09  5:49 dpdklab
2024-09-09  5:40 dpdklab
2024-09-09  5:22 dpdklab
2024-09-09  5:05 dpdklab
2024-09-09  4:39 dpdklab
2024-09-09  4:36 dpdklab
2024-09-08  7:05 dpdklab
2024-09-08  6:52 dpdklab
2024-09-08  5:42 dpdklab
2024-09-08  4:53 dpdklab
2024-09-08  4:53 dpdklab
2024-09-08  4:21 dpdklab
2024-09-08  4:20 dpdklab
2024-09-07 17:14 dpdklab
2024-09-07 15:47 dpdklab
2024-09-07  7:49 dpdklab
2024-09-07  6:21 dpdklab
2024-09-07  6:05 dpdklab
2024-09-07  4:57 dpdklab
2024-09-07  4:35 dpdklab
2024-09-07  4:27 dpdklab
2024-09-07  4:27 dpdklab
2024-09-07  1:22 dpdklab
2024-09-06 11:27 dpdklab
2024-09-06 11:22 dpdklab
2024-09-06 11:20 dpdklab
2024-09-06 11:14 dpdklab
2024-09-06 11:12 dpdklab
2024-09-06 11:11 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=66e281ee.050a0220.cbe8.4f23SMTPIN_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).