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, Akhil Goyal <gakhil@marvell.com>
Subject: |SUCCESS| [GIT MASTER] f4ccce58c1a33cb41e1e820da504698437987efc
Date: Thu, 21 Nov 2024 10:52:17 -0800 (PST)	[thread overview]
Message-ID: <673f8161.170a0220.23ed4f.0ad6SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Functional Testing PASS_

Branch: dpdk-next-crypto

f4ccce58c1a33cb41e1e820da504698437987efc --> functional testing pass

Upstream job id: Template-DTS-Pipeline#198088

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


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-11-21 18:52 UTC|newest]

Thread overview: 82+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-21 18:52 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-21 23:58 dpdklab
2024-11-21 23:49 dpdklab
2024-11-21 23:47 dpdklab
2024-11-21 23:41 dpdklab
2024-11-21 23:39 dpdklab
2024-11-21 23:11 dpdklab
2024-11-21 23:09 dpdklab
2024-11-21 22:58 dpdklab
2024-11-21 22:58 dpdklab
2024-11-21 22:55 dpdklab
2024-11-21 22:49 dpdklab
2024-11-21 22:46 dpdklab
2024-11-21 22:12 dpdklab
2024-11-21 21:55 dpdklab
2024-11-21 21:45 dpdklab
2024-11-21 21:37 dpdklab
2024-11-21 21:25 dpdklab
2024-11-21 21:18 dpdklab
2024-11-21 21:10 dpdklab
2024-11-21 21:10 dpdklab
2024-11-21 21:01 dpdklab
2024-11-21 20:43 dpdklab
2024-11-21 20:40 dpdklab
2024-11-21 20:19 dpdklab
2024-11-21 20:14 dpdklab
2024-11-21 20:14 dpdklab
2024-11-21 20:05 dpdklab
2024-11-21 19:50 dpdklab
2024-11-21 19:49 dpdklab
2024-11-21 19:46 dpdklab
2024-11-21 19:39 dpdklab
2024-11-21 19:38 dpdklab
2024-11-21 19:33 dpdklab
2024-11-21 19:30 dpdklab
2024-11-21 19:22 dpdklab
2024-11-21 19:22 dpdklab
2024-11-21 19:04 dpdklab
2024-11-21 18:58 dpdklab
2024-11-21 18:44 dpdklab
2024-11-21 18:41 dpdklab
2024-11-21 18:39 dpdklab
2024-11-21 18:37 dpdklab
2024-11-21 18:31 dpdklab
2024-11-21 18:29 dpdklab
2024-11-21 18:23 dpdklab
2024-11-21 18:21 dpdklab
2024-11-21 18:21 dpdklab
2024-11-21 18:19 dpdklab
2024-11-21 18:16 dpdklab
2024-11-21 18:08 dpdklab
2024-11-21 18:01 dpdklab
2024-11-21 17:58 dpdklab
2024-11-21 17:54 dpdklab
2024-11-21 17:52 dpdklab
2024-11-21 17:50 dpdklab
2024-11-21 17:43 dpdklab
2024-11-21 15:06 dpdklab
2024-11-21 12:47 dpdklab
2024-11-21 12:43 dpdklab
2024-11-21 12:43 dpdklab
2024-11-21 12:39 dpdklab
2024-11-21 12:28 dpdklab
2024-11-21 12:26 dpdklab
2024-11-21 12:19 dpdklab
2024-11-21 12:16 dpdklab
2024-11-21 12:07 dpdklab
2024-11-21 12:03 dpdklab
2024-11-21 12:02 dpdklab
2024-11-21  9:56 dpdklab
2024-11-21  9:46 dpdklab
2024-11-21  9:09 dpdklab
2024-11-21  8:48 dpdklab
2024-11-21  8:47 dpdklab
2024-11-21  8:46 dpdklab
2024-11-21  8:24 dpdklab
2024-11-21  8:23 dpdklab
2024-11-21  8:16 dpdklab
2024-11-21  8:10 dpdklab
2024-11-21  8:01 dpdklab
2024-11-21  7:58 dpdklab
2024-11-21  7:52 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=673f8161.170a0220.23ed4f.0ad6SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=gakhil@marvell.com \
    --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).