From: dpdklab@iol.unh.edu
To: Ferruh Yigit <ferruh.yigit@intel.com>,
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>
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] eeb0605f118dae66e80faa44f7b3e88748032353
Date: Thu, 29 Feb 2024 23:05:20 -0800 (PST) [thread overview]
Message-ID: <65e17e30.0d0a0220.71af6.b3bdSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing issues_
Branch: tags/v23.11
eeb0605f118dae66e80faa44f7b3e88748032353 --> functional testing fail
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 1/2
Failed Tests:
- mtu_update
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28252/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-03-01 7:05 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 7:05 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-04 5:52 dpdklab
2024-03-04 5:48 dpdklab
2024-03-04 5:35 dpdklab
2024-03-04 5:35 dpdklab
2024-03-01 20:03 dpdklab
2024-03-01 17:24 dpdklab
2024-03-01 6:52 dpdklab
2024-03-01 6:33 dpdklab
2024-02-29 5:30 dpdklab
2024-01-17 23:07 dpdklab
2024-01-17 6:40 dpdklab
2024-01-17 6:40 dpdklab
2024-01-17 6:40 dpdklab
2024-01-17 6:37 dpdklab
2024-01-17 6:34 dpdklab
2024-01-17 6:29 dpdklab
2024-01-17 6:29 dpdklab
2024-01-17 6:24 dpdklab
2024-01-17 6:22 dpdklab
2024-01-17 6:22 dpdklab
2024-01-17 6:15 dpdklab
2024-01-17 5:51 dpdklab
2024-01-17 5:50 dpdklab
2024-01-17 5:46 dpdklab
2024-01-11 7:55 dpdklab
2024-01-11 7:51 dpdklab
2024-01-11 7:42 dpdklab
2024-01-11 7:39 dpdklab
2024-01-11 7:34 dpdklab
2024-01-11 7:07 dpdklab
2024-01-11 7:05 dpdklab
2024-01-11 7:03 dpdklab
2024-01-11 7:03 dpdklab
2024-01-11 7:02 dpdklab
2024-01-11 6:47 dpdklab
2024-01-11 6:42 dpdklab
2024-01-11 6:39 dpdklab
2024-01-11 6:34 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=65e17e30.0d0a0220.71af6.b3bdSMTPIN_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).