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] caf0f5d395d99f48550aa345e7c920fba34a42a2
Date: Fri, 01 Mar 2024 08:54:53 -0800 (PST) [thread overview]
Message-ID: <65e2085d.4a0a0220.fd8ba.d546SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing issues_
Branch: tags/v22.11
caf0f5d395d99f48550aa345e7c920fba34a42a2 --> 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
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 9.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28254/
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 16:54 UTC|newest]
Thread overview: 253+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 16:54 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-01 6:41 dpdklab
2024-03-01 6:36 dpdklab
2024-03-01 6:30 dpdklab
2024-02-15 7:17 dpdklab
2024-02-15 7:16 dpdklab
2024-02-15 7:05 dpdklab
2024-02-15 7:03 dpdklab
2024-02-15 6:54 dpdklab
2024-02-15 6:53 dpdklab
2024-02-15 6:45 dpdklab
2024-02-15 6:34 dpdklab
2024-02-15 6:32 dpdklab
2024-02-15 6:31 dpdklab
2024-02-15 6:30 dpdklab
2024-02-15 6:28 dpdklab
2024-02-15 6:28 dpdklab
2024-02-15 6:17 dpdklab
2024-02-15 6:01 dpdklab
2024-02-15 6:01 dpdklab
2024-02-15 5:59 dpdklab
2024-02-15 5:58 dpdklab
2024-02-15 5:57 dpdklab
2024-02-15 5:56 dpdklab
2024-02-15 5:55 dpdklab
2024-02-15 5:55 dpdklab
2024-02-15 5:37 dpdklab
2024-02-15 5:34 dpdklab
2024-02-14 8:00 dpdklab
2024-02-14 7:30 dpdklab
2024-02-14 7:12 dpdklab
2024-02-14 7:05 dpdklab
2024-02-14 7:04 dpdklab
2024-02-14 7:01 dpdklab
2024-02-14 6:58 dpdklab
2024-02-14 6:58 dpdklab
2024-02-14 6:58 dpdklab
2024-02-14 6:57 dpdklab
2024-02-14 6:56 dpdklab
2024-02-14 6:55 dpdklab
2024-02-14 6:53 dpdklab
2024-02-14 6:52 dpdklab
2024-02-14 6:52 dpdklab
2024-02-14 6:49 dpdklab
2024-02-14 6:45 dpdklab
2024-02-14 6:44 dpdklab
2024-02-14 6:40 dpdklab
2024-02-14 6:40 dpdklab
2024-02-14 6:39 dpdklab
2024-02-14 6:33 dpdklab
2024-02-14 6:23 dpdklab
2024-02-14 6:22 dpdklab
2024-02-13 7:33 dpdklab
2024-02-13 7:27 dpdklab
2024-02-13 7:26 dpdklab
2024-02-13 7:25 dpdklab
2024-02-13 7:12 dpdklab
2024-02-13 7:12 dpdklab
2024-02-13 7:11 dpdklab
2024-02-13 7:00 dpdklab
2024-02-13 6:59 dpdklab
2024-02-13 6:58 dpdklab
2024-02-13 6:55 dpdklab
2024-02-13 6:53 dpdklab
2024-02-13 6:33 dpdklab
2024-02-13 6:25 dpdklab
2024-02-13 6:24 dpdklab
2024-02-13 6:24 dpdklab
2024-02-13 6:23 dpdklab
2024-02-13 6:19 dpdklab
2024-02-13 6:19 dpdklab
2024-02-13 6:19 dpdklab
2024-02-13 6:19 dpdklab
2024-02-13 6:16 dpdklab
2024-02-13 6:13 dpdklab
2024-02-12 6:41 dpdklab
2024-02-12 6:40 dpdklab
2024-02-12 6:38 dpdklab
2024-02-12 6:38 dpdklab
2024-02-12 6:38 dpdklab
2024-02-12 6:38 dpdklab
2024-02-12 6:38 dpdklab
2024-02-12 6:37 dpdklab
2024-02-12 6:36 dpdklab
2024-02-12 6:33 dpdklab
2024-02-12 6:30 dpdklab
2024-02-12 6:30 dpdklab
2024-02-12 6:28 dpdklab
2024-02-12 6:26 dpdklab
2024-02-12 6:26 dpdklab
2024-02-12 6:24 dpdklab
2024-02-12 6:23 dpdklab
2024-02-12 6:23 dpdklab
2024-02-12 6:22 dpdklab
2024-02-12 6:21 dpdklab
2024-02-12 6:20 dpdklab
2024-02-12 6:18 dpdklab
2024-02-11 7:28 dpdklab
2024-02-11 7:22 dpdklab
2024-02-11 7:04 dpdklab
2024-02-11 6:57 dpdklab
2024-02-11 6:53 dpdklab
2024-02-11 6:52 dpdklab
2024-02-11 6:52 dpdklab
2024-02-11 6:51 dpdklab
2024-02-11 6:50 dpdklab
2024-02-11 6:44 dpdklab
2024-02-11 6:38 dpdklab
2024-02-11 6:38 dpdklab
2024-02-11 6:36 dpdklab
2024-02-11 6:36 dpdklab
2024-02-11 6:26 dpdklab
2024-02-11 6:22 dpdklab
2024-02-10 7:27 dpdklab
2024-02-10 7:13 dpdklab
2024-02-10 7:10 dpdklab
2024-02-10 6:55 dpdklab
2024-02-10 6:54 dpdklab
2024-02-10 6:53 dpdklab
2024-02-10 6:44 dpdklab
2024-02-10 6:43 dpdklab
2024-02-10 6:38 dpdklab
2024-02-10 6:37 dpdklab
2024-02-10 6:36 dpdklab
2024-02-10 6:25 dpdklab
2024-02-10 6:23 dpdklab
2024-02-10 6:22 dpdklab
2024-02-10 6:20 dpdklab
2024-02-10 6:18 dpdklab
2024-02-10 6:18 dpdklab
2024-02-10 6:14 dpdklab
2024-02-10 6:13 dpdklab
2024-02-10 6:05 dpdklab
2024-02-10 6:05 dpdklab
2024-02-10 6:04 dpdklab
2024-02-10 6:02 dpdklab
2024-02-09 7:40 dpdklab
2024-02-09 7:16 dpdklab
2024-02-09 7:12 dpdklab
2024-02-09 7:03 dpdklab
2024-02-09 7:02 dpdklab
2024-02-09 6:52 dpdklab
2024-02-09 6:51 dpdklab
2024-02-09 6:49 dpdklab
2024-02-09 6:49 dpdklab
2024-02-09 6:45 dpdklab
2024-02-09 6:45 dpdklab
2024-02-09 6:43 dpdklab
2024-02-09 6:37 dpdklab
2024-02-09 6:29 dpdklab
2024-02-09 6:26 dpdklab
2024-02-09 6:22 dpdklab
2024-02-08 7:01 dpdklab
2024-02-08 6:59 dpdklab
2024-02-08 6:52 dpdklab
2024-02-08 6:46 dpdklab
2024-02-08 6:45 dpdklab
2024-02-08 6:44 dpdklab
2024-02-08 6:44 dpdklab
2024-02-08 6:39 dpdklab
2024-02-08 6:37 dpdklab
2024-02-08 6:33 dpdklab
2024-02-08 6:32 dpdklab
2024-02-08 6:22 dpdklab
2024-02-08 6:22 dpdklab
2024-02-08 6:20 dpdklab
2024-02-08 6:16 dpdklab
2024-02-08 6:15 dpdklab
2024-02-08 6:15 dpdklab
2024-02-08 6:14 dpdklab
2024-02-08 6:14 dpdklab
2024-02-08 6:11 dpdklab
2024-02-08 6:10 dpdklab
2024-02-08 6:05 dpdklab
2024-02-08 6:05 dpdklab
2024-02-07 7:03 dpdklab
2024-02-07 6:57 dpdklab
2024-02-07 6:57 dpdklab
2024-02-07 6:56 dpdklab
2024-02-07 6:56 dpdklab
2024-02-07 6:56 dpdklab
2024-02-07 6:56 dpdklab
2024-02-07 6:55 dpdklab
2024-02-07 6:55 dpdklab
2024-02-07 6:52 dpdklab
2024-02-07 6:43 dpdklab
2024-02-07 6:42 dpdklab
2024-02-06 6:24 dpdklab
2024-02-06 6:24 dpdklab
2024-02-06 6:23 dpdklab
2024-02-06 6:19 dpdklab
2024-02-06 6:19 dpdklab
2024-02-06 6:15 dpdklab
2024-02-06 6:10 dpdklab
2024-02-06 6:08 dpdklab
2024-02-06 6:07 dpdklab
2024-02-06 6:07 dpdklab
2024-02-06 6:07 dpdklab
2024-02-06 6:06 dpdklab
2024-02-06 6:04 dpdklab
2024-02-06 6:03 dpdklab
2024-02-06 5:51 dpdklab
2024-02-05 6:42 dpdklab
2024-02-05 6:38 dpdklab
2024-02-05 6:34 dpdklab
2024-02-05 6:20 dpdklab
2024-02-05 6:13 dpdklab
2024-02-05 6:12 dpdklab
2024-02-05 6:11 dpdklab
2024-02-04 6:59 dpdklab
2024-02-03 7:19 dpdklab
2024-02-03 6:50 dpdklab
2024-02-03 6:49 dpdklab
2024-02-03 6:36 dpdklab
2024-02-03 6:34 dpdklab
2024-02-03 6:31 dpdklab
2024-02-03 6:30 dpdklab
2024-02-03 6:28 dpdklab
2024-02-03 6:27 dpdklab
2024-02-02 8:52 dpdklab
2024-02-01 7:14 dpdklab
2024-02-01 6:59 dpdklab
2024-01-31 7:06 dpdklab
2024-01-31 7:02 dpdklab
2024-01-31 6:45 dpdklab
2024-01-31 6:40 dpdklab
2024-01-31 6:35 dpdklab
2024-01-31 6:33 dpdklab
2024-01-31 6:29 dpdklab
2024-01-30 10:28 dpdklab
2024-01-30 10:22 dpdklab
2024-01-30 10:15 dpdklab
2024-01-30 9:53 dpdklab
2024-01-30 9:36 dpdklab
2024-01-30 9:22 dpdklab
2024-01-29 6:25 dpdklab
2024-01-29 6:21 dpdklab
2024-01-29 6:11 dpdklab
2024-01-28 6:45 dpdklab
2024-01-27 7:26 dpdklab
2024-01-27 5:59 dpdklab
2024-01-27 5:57 dpdklab
2024-01-27 5:52 dpdklab
2024-01-26 8:58 dpdklab
2024-01-25 8:36 dpdklab
2024-01-24 7:19 dpdklab
2024-01-24 7:03 dpdklab
2024-01-24 6:50 dpdklab
2024-01-24 6:45 dpdklab
2024-01-24 6:44 dpdklab
2024-01-24 6:42 dpdklab
2024-01-24 6:42 dpdklab
2024-01-24 6: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=65e2085d.4a0a0220.fd8ba.d546SMTPIN_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).