automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>,
	Georgii Tkachuk <georgii.tkachuk@intel.com>,
	Qian Xu <qian.q.xu@intel.com>, Lijuan Tu <lijuan.tu@intel.com>,
	Ferruh Yigit <ferruh.yigit@intel.com>
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: |FAILURE| [GIT MASTER] f197f1e13ccfb74c92ad05602443dd0984f39540
Date: Mon, 09 Dec 2024 22:14:47 -0800 (PST)	[thread overview]
Message-ID: <6757dc57.630a0220.96737.fbc6SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Functional Testing issues_

Branch: tags/v21.11

f197f1e13ccfb74c92ad05602443dd0984f39540 --> functional testing issues

Upstream job id: Template-DTS-Pipeline#201755

Test environment and result as below:

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


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-12-10  6:14 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-10  6:14 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-11  8:10 dpdklab
2024-12-11  7:59 dpdklab
2024-12-11  7:58 dpdklab
2024-12-11  7:58 dpdklab
2024-12-11  7:57 dpdklab
2024-12-11  7:57 dpdklab
2024-12-11  7:54 dpdklab
2024-12-11  7:42 dpdklab
2024-12-11  7:42 dpdklab
2024-12-11  7:37 dpdklab
2024-12-11  7:36 dpdklab
2024-12-11  7:29 dpdklab
2024-12-11  7:23 dpdklab
2024-12-10  7:36 dpdklab
2024-12-10  7:28 dpdklab
2024-12-10  7:25 dpdklab
2024-12-10  7:25 dpdklab
2024-12-10  7:22 dpdklab
2024-12-10  7:21 dpdklab
2024-12-10  7:19 dpdklab
2024-12-10  7:17 dpdklab
2024-12-10  7:12 dpdklab
2024-12-10  7:12 dpdklab
2024-12-10  7:06 dpdklab
2024-12-10  6:28 dpdklab
2024-12-10  6:05 dpdklab
2024-12-10  6:02 dpdklab
2024-12-09  7:21 dpdklab
2024-12-09  7:15 dpdklab
2024-12-09  7:10 dpdklab
2024-12-09  7:09 dpdklab
2024-12-09  7:06 dpdklab
2024-12-09  7:04 dpdklab
2024-12-09  7:04 dpdklab
2024-12-09  7:02 dpdklab
2024-12-09  7:00 dpdklab
2024-12-09  6:59 dpdklab
2024-12-09  6:57 dpdklab
2024-12-09  6:35 dpdklab
2024-12-09  5:42 dpdklab
2024-12-09  5:26 dpdklab
2024-12-08  7:06 dpdklab
2024-12-08  6:33 dpdklab
2024-12-08  6:32 dpdklab
2024-12-08  6:30 dpdklab
2024-12-08  6:20 dpdklab
2024-12-08  6:17 dpdklab
2024-12-08  6:13 dpdklab
2024-12-08  6:10 dpdklab
2024-12-08  6:10 dpdklab
2024-12-08  6:07 dpdklab
2024-12-08  6:04 dpdklab
2024-12-08  6:03 dpdklab
2024-12-08  5:52 dpdklab
2024-12-07  8:06 dpdklab
2024-12-07  8:04 dpdklab
2024-12-07  7:59 dpdklab
2024-12-07  7:52 dpdklab
2024-12-07  7:52 dpdklab
2024-12-07  7:48 dpdklab
2024-12-07  7:44 dpdklab
2024-12-07  7:43 dpdklab
2024-12-07  7:40 dpdklab
2024-12-07  7:37 dpdklab
2024-12-07  7:37 dpdklab
2024-12-07  7:34 dpdklab
2024-12-06  7:00 dpdklab
2024-12-06  6:59 dpdklab
2024-12-06  6:56 dpdklab
2024-12-06  6:51 dpdklab
2024-12-06  6:40 dpdklab
2024-12-06  6:37 dpdklab
2024-12-06  6:37 dpdklab
2024-12-06  6:36 dpdklab
2024-12-06  6:26 dpdklab
2024-12-06  6:25 dpdklab
2024-12-06  5:40 dpdklab
2024-12-06  5:37 dpdklab
2024-12-06  5:26 dpdklab
2024-12-05  9:28 dpdklab
2024-12-05  8:49 dpdklab
2024-12-05  8:43 dpdklab
2024-12-05  8:37 dpdklab
2024-12-05  8:37 dpdklab
2024-12-05  8:33 dpdklab
2024-12-05  8:32 dpdklab
2024-12-05  8:30 dpdklab
2024-12-05  8:29 dpdklab
2024-12-05  8:27 dpdklab
2024-12-05  8:27 dpdklab
2024-12-05  8:19 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=6757dc57.630a0220.96737.fbc6SMTPIN_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=ferruh.yigit@intel.com \
    --cc=georgii.tkachuk@intel.com \
    --cc=ktraynor@redhat.com \
    --cc=lijuan.tu@intel.com \
    --cc=qian.q.xu@intel.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).