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, Gregory Etelson <getelson@nvidia.com>
Subject: |FAILURE| pw139758 [PATCH] cmdline: configure input buffer size
Date: Sat, 04 May 2024 04:42:06 -0700 (PDT) [thread overview]
Message-ID: <66361f0e.c50a0220.21f43.ff89SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240501052659.231457-1-getelson@nvidia.com>
Test-Label: iol-intel-Functional
Test-Status: FAILURE
http://dpdk.org/patch/139758
_Functional Testing issues_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Wednesday, May 01 2024 05:26:59
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:7e06c0de1952d3109a5b0c4779d7e7d8059c9d78
139758 --> functional testing fail
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
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 XL710-QDA2 40000 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
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
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/patchsets/29885/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
prev parent reply other threads:[~2024-05-04 11:42 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240501052659.231457-1-getelson@nvidia.com>
2024-05-01 5:08 ` |SUCCESS| " qemudev
2024-05-01 5:13 ` qemudev
2024-05-01 6:23 ` 0-day Robot
2024-05-01 6:29 ` dpdklab
2024-05-01 6:30 ` dpdklab
2024-05-01 6:30 ` dpdklab
2024-05-01 6:31 ` dpdklab
2024-05-01 6:31 ` dpdklab
2024-05-01 6:31 ` |FAILURE| " dpdklab
2024-05-01 6:31 ` |SUCCESS| " dpdklab
2024-05-01 6:32 ` |FAILURE| " dpdklab
2024-05-01 6:32 ` |SUCCESS| " dpdklab
2024-05-01 6:32 ` dpdklab
2024-05-01 6:32 ` |FAILURE| " dpdklab
2024-05-01 6:33 ` |SUCCESS| " dpdklab
2024-05-01 6:33 ` dpdklab
2024-05-01 6:34 ` dpdklab
2024-05-01 6:34 ` dpdklab
2024-05-01 6:35 ` dpdklab
2024-05-01 6:35 ` dpdklab
2024-05-01 6:35 ` dpdklab
2024-05-01 6:35 ` dpdklab
2024-05-01 6:36 ` dpdklab
2024-05-01 6:36 ` dpdklab
2024-05-01 6:36 ` dpdklab
2024-05-01 6:36 ` dpdklab
2024-05-01 6:36 ` dpdklab
2024-05-01 6:37 ` dpdklab
2024-05-01 6:37 ` dpdklab
2024-05-01 6:37 ` dpdklab
2024-05-01 6:37 ` dpdklab
2024-05-01 6:37 ` dpdklab
2024-05-01 6:38 ` dpdklab
2024-05-01 6:38 ` dpdklab
2024-05-01 6:39 ` dpdklab
2024-05-01 6:39 ` dpdklab
2024-05-01 6:39 ` dpdklab
2024-05-01 6:40 ` dpdklab
2024-05-01 6:40 ` dpdklab
2024-05-01 6:40 ` dpdklab
2024-05-01 6:40 ` dpdklab
2024-05-01 6:40 ` dpdklab
2024-05-01 6:42 ` dpdklab
2024-05-01 6:42 ` dpdklab
2024-05-01 6:43 ` dpdklab
2024-05-01 6:43 ` dpdklab
2024-05-01 6:43 ` dpdklab
2024-05-01 6:45 ` dpdklab
2024-05-01 6:46 ` dpdklab
2024-05-01 6:47 ` dpdklab
2024-05-01 6:48 ` dpdklab
2024-05-01 6:49 ` dpdklab
2024-05-01 6:49 ` dpdklab
2024-05-01 6:51 ` dpdklab
2024-05-01 6:51 ` dpdklab
2024-05-01 6:53 ` dpdklab
2024-05-01 6:54 ` dpdklab
2024-05-01 6:54 ` dpdklab
2024-05-01 6:56 ` dpdklab
2024-05-01 6:58 ` dpdklab
2024-05-01 6:58 ` dpdklab
2024-05-01 6:59 ` dpdklab
2024-05-01 7:00 ` dpdklab
2024-05-01 7:00 ` dpdklab
2024-05-01 7:00 ` dpdklab
2024-05-01 7:01 ` dpdklab
2024-05-01 7:03 ` dpdklab
2024-05-01 7:05 ` dpdklab
2024-05-01 7:06 ` dpdklab
2024-05-01 7:07 ` dpdklab
2024-05-01 7:09 ` dpdklab
2024-05-01 7:11 ` dpdklab
2024-05-01 7:11 ` dpdklab
2024-05-01 7:12 ` dpdklab
2024-05-01 7:17 ` dpdklab
2024-05-01 7:18 ` dpdklab
2024-05-01 7:23 ` dpdklab
2024-05-01 7:23 ` dpdklab
2024-05-01 7:23 ` dpdklab
2024-05-01 7:25 ` dpdklab
2024-05-01 7:43 ` dpdklab
2024-05-01 7:44 ` dpdklab
2024-05-01 9:02 ` dpdklab
2024-05-01 9:34 ` dpdklab
2024-05-04 0:29 ` dpdklab
2024-05-04 11:10 ` dpdklab
2024-05-04 11:15 ` |FAILURE| " dpdklab
2024-05-04 11:19 ` |SUCCESS| " dpdklab
2024-05-04 11:22 ` dpdklab
2024-05-04 11:42 ` dpdklab [this message]
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=66361f0e.c50a0220.21f43.ff89SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ferruh.yigit@intel.com \
--cc=georgii.tkachuk@intel.com \
--cc=getelson@nvidia.com \
--cc=lijuan.tu@intel.com \
--cc=qian.q.xu@intel.com \
--cc=test-report@dpdk.org \
/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).