From: dpdklab@iol.unh.edu
To: Georgii Tkachuk <georgii.tkachuk@intel.com>,
Qian Xu <qian.q.xu@intel.com>, Lijuan Tu <lijuan.tu@intel.com>,
Test Report <test-report@dpdk.org>,
Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dpdk-test-reports@iol.unh.edu,
Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Subject: |FAILURE| pw137678 [PATCH] [v5] common/qat: add virtual qat device (
Date: Fri, 01 Mar 2024 14:49:59 -0800 (PST) [thread overview]
Message-ID: <65e25b97.170a0220.ec8e6.21beSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240301151923.4906-1-arkadiuszx.kusztal@intel.com>
Test-Label: iol-intel-Functional
Test-Status: FAILURE
http://dpdk.org/patch/137678
_Functional Testing issues_
Submitter: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Date: Friday, March 01 2024 15:19:23
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:5ac50824383c2683c0dfdf24c6dc493f1fa54852
137678 --> functional testing fail
Test environment and result as below:
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
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/3
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29375/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-03-01 22:50 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240301151923.4906-1-arkadiuszx.kusztal@intel.com>
2024-03-01 15:21 ` |SUCCESS| pw137678 [PATCH v5] common/qat: add virtual qat device vQAT checkpatch
2024-03-01 22:21 ` |SUCCESS| pw137678 [PATCH] [v5] common/qat: add virtual qat device ( dpdklab
2024-03-01 22:40 ` dpdklab
2024-03-01 22:42 ` dpdklab
2024-03-01 22:46 ` dpdklab
2024-03-01 22:49 ` dpdklab [this message]
2024-03-01 22:50 ` |FAILURE| " dpdklab
2024-03-01 22:53 ` |SUCCESS| " dpdklab
2024-03-01 22:54 ` dpdklab
2024-03-01 23:06 ` dpdklab
2024-03-01 23:06 ` dpdklab
2024-03-01 23:15 ` dpdklab
2024-03-01 23:16 ` dpdklab
2024-03-01 23:17 ` dpdklab
2024-03-01 23:17 ` dpdklab
2024-03-01 23:17 ` dpdklab
2024-03-01 23:17 ` dpdklab
2024-03-01 23:18 ` dpdklab
2024-03-01 23:25 ` |FAILURE| " dpdklab
2024-03-01 23:52 ` |SUCCESS| " dpdklab
2024-03-01 23:55 ` dpdklab
2024-03-01 23:56 ` |FAILURE| " dpdklab
2024-03-01 23:57 ` |SUCCESS| " dpdklab
2024-03-02 1:20 ` dpdklab
2024-03-02 1:20 ` dpdklab
2024-03-02 1:21 ` dpdklab
2024-03-02 1:21 ` dpdklab
2024-03-02 1:21 ` dpdklab
2024-03-02 1:22 ` dpdklab
2024-03-02 1:22 ` dpdklab
2024-03-02 1:22 ` dpdklab
2024-03-02 1:22 ` dpdklab
2024-03-02 1:22 ` dpdklab
2024-03-02 1:22 ` dpdklab
2024-03-02 1:23 ` dpdklab
2024-03-02 1:23 ` dpdklab
2024-03-02 1:25 ` dpdklab
2024-03-02 1:25 ` dpdklab
2024-03-02 1:25 ` dpdklab
2024-03-02 1:25 ` dpdklab
2024-03-02 1:26 ` dpdklab
2024-03-02 1:26 ` dpdklab
2024-03-02 1:27 ` dpdklab
2024-03-02 1:30 ` dpdklab
2024-03-02 1:37 ` dpdklab
2024-03-02 1:42 ` dpdklab
2024-03-02 1:42 ` dpdklab
2024-03-02 1:42 ` dpdklab
2024-03-02 1:43 ` dpdklab
2024-03-02 1:43 ` dpdklab
2024-03-02 1:43 ` dpdklab
2024-03-02 1:45 ` dpdklab
2024-03-02 1:45 ` dpdklab
2024-03-02 1:46 ` dpdklab
2024-03-02 1:51 ` dpdklab
2024-03-02 1:51 ` dpdklab
2024-03-02 1:52 ` dpdklab
2024-03-02 1:52 ` dpdklab
2024-03-02 1:52 ` dpdklab
2024-03-02 1:53 ` dpdklab
2024-03-02 1:53 ` dpdklab
2024-03-02 1:54 ` dpdklab
2024-03-02 1:55 ` dpdklab
2024-03-02 1:55 ` dpdklab
2024-03-02 1:59 ` dpdklab
2024-03-02 2:15 ` dpdklab
2024-03-02 2:20 ` dpdklab
2024-03-02 3:00 ` |SUCCESS| pw137678 [PATCH v5] common/qat: add virtual qat device (vQAT) qemudev
2024-03-02 3:04 ` qemudev
2024-03-02 4:02 ` |SUCCESS| pw137678 [PATCH] [v5] common/qat: add virtual qat device ( dpdklab
2024-03-02 4:32 ` dpdklab
2024-03-03 2:26 ` dpdklab
2024-03-04 6:16 ` dpdklab
2024-03-06 3:10 ` dpdklab
2024-03-06 3:43 ` dpdklab
2024-03-06 4:15 ` 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=65e25b97.170a0220.ec8e6.21beSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=arkadiuszx.kusztal@intel.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).