From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>,
Lijuan Tu <lijuan.tu@intel.com>,
Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dpdk-test-reports@iol.unh.edu,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ferruh Yigit <ferruh.yigit@amd.com>,
Ivan Malov <ivan.malov@arknetworks.am>
Subject: |FAILURE| pw123898 [PATCH] net/sfc: enforce fate action in transfer flow rules
Date: Wed, 15 Feb 2023 05:01:38 -0500 (EST) [thread overview]
Message-ID: <20230215100138.56637106182@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]
Test-Label: iol-intel-Functional
Test-Status: FAILURE
http://dpdk.org/patch/123898
_Functional Testing issues_
Submitter: Ivan Malov <ivan.malov@arknetworks.am>
Date: Tuesday, February 14 2023 13:12:47
DPDK git baseline: Repo:dpdk-next-net
Branch: master
CommitID:a2a8cb4251308ce5ccbe391576fe6483c3adbc4c
123898 --> functional testing fail
Test environment and result as below:
Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-137-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: 1/2
Failed Tests:
- unit_tests_mbuf
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/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25392/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-02-15 10:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 10:01 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-15 10:17 dpdklab
2023-02-15 10:02 dpdklab
2023-02-15 10:01 dpdklab
2023-02-15 9:57 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=20230215100138.56637106182@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ferruh.yigit@amd.com \
--cc=ferruh.yigit@intel.com \
--cc=ivan.malov@arknetworks.am \
--cc=lijuan.tu@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).