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] 802f39367e08d2916cd21f7b6a34703bc8672a38
Date: Fri, 22 Nov 2024 22:12:08 -0800 (PST)	[thread overview]
Message-ID: <67417238.170a0220.227cd2.8236SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Functional Testing PASS_

Branch: tags/v22.11

802f39367e08d2916cd21f7b6a34703bc8672a38 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#198436

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  |
+-----------------------------+--------+


Arm Ampere Altra - Ubuntu 22.04
Kernel: 5.15.83+
Compiler: gcc 11.4
NIC: Intel Corporation QAT 8970 0 Mbps

Aggregate Results by Test Suite
+----------------------------+--------+
|         Test Suite         | Result |
+============================+========+
| crypto_perf_cryptodev_perf |  PASS  |
+----------------------------+--------+


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-11-23  6:12 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-23  6:12 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-23 10:19 dpdklab
2024-11-23  8:49 dpdklab
2024-11-23  8:34 dpdklab
2024-11-23  7:46 dpdklab
2024-11-23  6:52 dpdklab
2024-11-23  6:38 dpdklab
2024-11-23  6:27 dpdklab
2024-11-23  6:06 dpdklab
2024-11-23  6:04 dpdklab
2024-11-23  5:34 dpdklab
2024-11-22 10:11 dpdklab
2024-11-22  8:29 dpdklab
2024-11-22  7:37 dpdklab
2024-11-22  7:14 dpdklab
2024-11-22  7:05 dpdklab
2024-11-22  6:36 dpdklab
2024-11-22  6:14 dpdklab
2024-11-22  6:05 dpdklab
2024-11-22  6:01 dpdklab
2024-11-22  5:50 dpdklab
2024-11-21  9:16 dpdklab
2024-11-21  9:03 dpdklab
2024-11-21  8:32 dpdklab
2024-11-21  7:53 dpdklab
2024-11-21  7:27 dpdklab
2024-11-21  7:26 dpdklab
2024-11-21  7:24 dpdklab
2024-11-21  7:20 dpdklab
2024-11-21  7:03 dpdklab
2024-11-21  6:55 dpdklab
2024-11-21  6:35 dpdklab
2024-11-21  6:26 dpdklab
2024-11-21  5:48 dpdklab
2024-11-20 13:16 dpdklab
2024-11-20 12:55 dpdklab
2024-11-20 12:40 dpdklab
2024-11-20 12:20 dpdklab
2024-11-20 11:59 dpdklab
2024-11-20 11:54 dpdklab
2024-11-20 11:36 dpdklab
2024-11-20 10:31 dpdklab
2024-11-20  9:55 dpdklab
2024-11-20  9:00 dpdklab
2024-11-20  7:43 dpdklab
2024-11-20  7:08 dpdklab
2024-11-20  7:06 dpdklab
2024-11-20  7:02 dpdklab
2024-11-20  6:12 dpdklab
2024-11-20  3:57 dpdklab
2024-11-20  2:24 dpdklab
2024-11-20  0:41 dpdklab
2024-11-20  0:08 dpdklab
2024-11-19 23:15 dpdklab
2024-11-19 23:12 dpdklab
2024-11-19 22:19 dpdklab
2024-11-19 21:55 dpdklab
2024-11-19 21:53 dpdklab
2024-11-19 21:52 dpdklab
2024-11-19 21:43 dpdklab
2024-11-19 21:42 dpdklab
2024-11-19 21:36 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=67417238.170a0220.227cd2.8236SMTPIN_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).