automatic DPDK test reports
 help / color / mirror / Atom feed
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] b0b971bf661967fdf3d06e56b5437a779c2915ae
Date: Sat, 04 May 2024 03:04:13 -0700 (PDT)	[thread overview]
Message-ID: <6636081d.050a0220.ec816.0ef2SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Functional Testing issues_

Branch: tags/v23.11

b0b971bf661967fdf3d06e56b5437a779c2915ae --> functional testing fail

Test environment and result as below:

Ubuntu 20.04 ARM
Kernel: 5.15.0-97-generic
Compiler: gcc 11.4.0
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: 5.4.0-122-generic
Compiler: gcc 9.4.0
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: 5.4.0-122-generic
Compiler: gcc 9.4.0
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 11.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


Arm Ampere Altra - Ubuntu 22.04
Kernel: 5.15.83+
Compiler: gcc 11.4
NIC: Intel Corporation QAT 8970 0 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-05-04 10:04 UTC|newest]

Thread overview: 110+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-04 10:04 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-07  7:55 dpdklab
2024-05-07  7:44 dpdklab
2024-05-07  7:43 dpdklab
2024-05-07  7:41 dpdklab
2024-05-07  7:33 dpdklab
2024-05-07  7:32 dpdklab
2024-05-07  7:31 dpdklab
2024-05-07  7:29 dpdklab
2024-05-07  7:28 dpdklab
2024-05-07  7:22 dpdklab
2024-05-07  7:07 dpdklab
2024-05-07  7:03 dpdklab
2024-05-07  6:32 dpdklab
2024-05-07  6:17 dpdklab
2024-05-04  9:44 dpdklab
2024-05-01  5:04 dpdklab
2024-05-01  4:41 dpdklab
2024-05-01  4:37 dpdklab
2024-04-29  5:14 dpdklab
2024-04-29  5:12 dpdklab
2024-04-29  5:10 dpdklab
2024-04-29  5:09 dpdklab
2024-04-29  5:09 dpdklab
2024-04-29  5:08 dpdklab
2024-04-29  5:07 dpdklab
2024-04-29  5:05 dpdklab
2024-04-29  5:00 dpdklab
2024-04-29  4:59 dpdklab
2024-04-29  4:57 dpdklab
2024-04-29  4:56 dpdklab
2024-04-26  6:37 dpdklab
2024-04-18  5:50 dpdklab
2024-04-18  5:43 dpdklab
2024-04-18  5:42 dpdklab
2024-04-18  5:40 dpdklab
2024-04-18  5:37 dpdklab
2024-04-18  5:37 dpdklab
2024-04-18  5:35 dpdklab
2024-04-18  5:34 dpdklab
2024-04-18  5:34 dpdklab
2024-04-18  5:33 dpdklab
2024-04-18  5:31 dpdklab
2024-04-18  5:29 dpdklab
2024-04-18  5:28 dpdklab
2024-04-18  5:26 dpdklab
2024-04-18  5:10 dpdklab
2024-04-17  5:23 dpdklab
2024-04-17  5:22 dpdklab
2024-04-17  5:22 dpdklab
2024-04-17  5:20 dpdklab
2024-04-17  5:20 dpdklab
2024-04-17  5:19 dpdklab
2024-04-17  5:17 dpdklab
2024-04-17  5:15 dpdklab
2024-04-17  5:15 dpdklab
2024-04-17  5:14 dpdklab
2024-04-17  5:12 dpdklab
2024-04-17  5:08 dpdklab
2024-04-17  5:05 dpdklab
2024-04-17  5:04 dpdklab
2024-04-17  4:44 dpdklab
2024-04-09  5:53 dpdklab
2024-04-09  5:44 dpdklab
2024-04-09  5:32 dpdklab
2024-04-09  5:31 dpdklab
2024-04-09  5:31 dpdklab
2024-04-09  5:27 dpdklab
2024-04-09  5:21 dpdklab
2024-04-09  5:18 dpdklab
2024-04-09  5:17 dpdklab
2024-04-09  5:17 dpdklab
2024-04-09  5:16 dpdklab
2024-04-09  5:12 dpdklab
2024-04-03  1:12 dpdklab
2024-03-30  7:00 dpdklab
2024-03-27  8:36 dpdklab
2024-03-27  7:56 dpdklab
2024-03-27  7:55 dpdklab
2024-03-27  7:54 dpdklab
2024-03-27  7:53 dpdklab
2024-03-27  7:37 dpdklab
2024-03-27  7:35 dpdklab
2024-03-27  7:32 dpdklab
2024-03-27  7:30 dpdklab
2024-03-27  7:08 dpdklab
2024-03-27  7:08 dpdklab
2024-03-27  7:05 dpdklab
2024-03-27  6:58 dpdklab
2024-03-27  5:41 dpdklab
2024-03-25  5:20 dpdklab
2024-03-25  5:08 dpdklab
2024-03-25  5:05 dpdklab
2024-03-25  5:04 dpdklab
2024-03-25  5:03 dpdklab
2024-03-25  5:00 dpdklab
2024-03-25  5:00 dpdklab
2024-03-25  5:00 dpdklab
2024-03-25  4:59 dpdklab
2024-03-25  4:48 dpdklab
2024-03-25  4:43 dpdklab
2024-03-25  4:41 dpdklab
2024-03-25  4:39 dpdklab
2024-03-16  7:11 dpdklab
2024-03-16  6:34 dpdklab
2024-03-16  6:01 dpdklab
2024-03-16  5:50 dpdklab
2024-03-16  5:46 dpdklab
2024-03-16  5:41 dpdklab
2024-03-16  5:35 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=6636081d.050a0220.ec816.0ef2SMTPIN_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).