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, Andrew Boyer <Andrew.Boyer@amd.com>
Subject: |FAILURE| pw136340-136352 [PATCH] [13/13] net/ionic: optimize device
Date: Fri, 02 Feb 2024 12:19:26 -0800 (PST) [thread overview]
Message-ID: <65bd4e4e.050a0220.63e1e.6270SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: FAILURE
http://dpdk.org/patch/136352
_Functional Testing issues_
Submitter: Andrew Boyer <Andrew.Boyer@amd.com>
Date: Friday, February 02 2024 19:32:38
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:f8ecc0053ca52cb2310a9e1834ea583167a793cd
136340-136352 --> 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/3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29044/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-02 20:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 20:19 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-05 20:14 dpdklab
2024-02-05 20:05 dpdklab
2024-02-05 19:52 dpdklab
2024-02-02 20:24 dpdklab
2024-02-02 20:22 dpdklab
2024-02-02 20:14 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=65bd4e4e.050a0220.63e1e.6270SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=Andrew.Boyer@amd.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ferruh.yigit@intel.com \
--cc=georgii.tkachuk@intel.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).