From: dpdklab@iol.unh.edu
To: Lijuan Tu <lijuan.tu@intel.com>,
Test Report <test-report@dpdk.org>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Georgii Tkachuk <georgii.tkachuk@intel.com>,
Qian Xu <qian.q.xu@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] b40fd60a9d5b99d165aeeb09a43df2e404d9ec05
Date: Wed, 28 Aug 2024 12:53:01 -0700 (PDT) [thread overview]
Message-ID: <66cf801d.050a0220.2cd221.0437SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing issues_
Branch: 21.11-staging
b40fd60a9d5b99d165aeeb09a43df2e404d9ec05 --> functional testing issues
Upstream job id: Template-DTS-Pipeline#177467
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 |
+-----------------------------+--------+
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 11.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter | FAIL |
+------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/30383/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-08-28 19:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 19:53 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-19 16:56 dpdklab
2024-08-28 21:14 dpdklab
2024-08-28 20:53 dpdklab
2024-08-28 20:34 dpdklab
2024-08-28 20:29 dpdklab
2024-08-28 20:26 dpdklab
2024-08-28 20:26 dpdklab
2024-08-28 20:19 dpdklab
2024-08-28 20:15 dpdklab
2024-08-28 20:14 dpdklab
2024-08-28 20:04 dpdklab
2024-08-28 20:04 dpdklab
2024-08-28 20:01 dpdklab
2024-08-28 19:48 dpdklab
2024-08-28 19:47 dpdklab
2024-08-28 19:47 dpdklab
2024-08-28 19:46 dpdklab
2024-08-28 19:38 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=66cf801d.050a0220.2cd221.0437SMTPIN_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).