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,
Stephen Hemminger <stephen@networkplumber.org>
Subject: |FAILURE| pw137691-137761 [PATCH] [v2,71/71] examples: replace use o
Date: Fri, 01 Mar 2024 15:18:18 -0800 (PST) [thread overview]
Message-ID: <65e2623a.170a0220.ff040.84c2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240301171707.95242-72-stephen@networkplumber.org>
Test-Label: iol-intel-Functional
Test-Status: FAILURE
http://dpdk.org/patch/137761
_Functional Testing issues_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Friday, March 01 2024 17:16:07
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:5df34de5808a7b826b8bc035d6ee3161a12be364
137691-137761 --> 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
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-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: 0/1
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/29380/
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 23:18 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240301171707.95242-72-stephen@networkplumber.org>
2024-03-01 17:26 ` |WARNING| pw137761 [PATCH v2 71/71] examples: replace use of fixed size rte_memcpy checkpatch
2024-03-01 18:24 ` |SUCCESS| " 0-day Robot
2024-03-01 21:01 ` |SUCCESS| pw137691-137761 [PATCH] [v2,71/71] examples: replace use o dpdklab
2024-03-01 21:06 ` dpdklab
2024-03-01 21:09 ` |FAILURE| " dpdklab
2024-03-01 21:10 ` |SUCCESS| " dpdklab
2024-03-01 21:15 ` |FAILURE| " dpdklab
2024-03-01 21:25 ` |SUCCESS| " dpdklab
2024-03-01 21:34 ` dpdklab
2024-03-01 21:36 ` dpdklab
2024-03-01 21:37 ` dpdklab
2024-03-01 21:46 ` dpdklab
2024-03-01 21:47 ` |FAILURE| " dpdklab
2024-03-01 21:48 ` |SUCCESS| " dpdklab
2024-03-01 21:49 ` dpdklab
2024-03-01 21:52 ` dpdklab
2024-03-01 21:54 ` dpdklab
2024-03-01 21:55 ` dpdklab
2024-03-01 22:01 ` dpdklab
2024-03-01 22:15 ` dpdklab
2024-03-01 23:16 ` dpdklab
2024-03-01 23:16 ` dpdklab
2024-03-01 23:18 ` dpdklab [this message]
2024-03-01 23:19 ` dpdklab
2024-03-01 23:59 ` dpdklab
2024-03-02 0:02 ` dpdklab
2024-03-02 0:02 ` dpdklab
2024-03-02 0:03 ` dpdklab
2024-03-02 0:04 ` dpdklab
2024-03-02 0:09 ` dpdklab
2024-03-02 0:11 ` dpdklab
2024-03-02 0:11 ` dpdklab
2024-03-02 0:11 ` dpdklab
2024-03-02 0:11 ` dpdklab
2024-03-02 0:12 ` dpdklab
2024-03-02 0:13 ` dpdklab
2024-03-02 0:13 ` dpdklab
2024-03-02 0:14 ` dpdklab
2024-03-02 0:15 ` dpdklab
2024-03-02 0:15 ` dpdklab
2024-03-02 0:16 ` dpdklab
2024-03-02 0:16 ` dpdklab
2024-03-02 0:16 ` dpdklab
2024-03-02 0:16 ` dpdklab
2024-03-02 0:17 ` dpdklab
2024-03-02 0:17 ` dpdklab
2024-03-02 0:36 ` dpdklab
2024-03-02 0:37 ` dpdklab
2024-03-02 0:38 ` dpdklab
2024-03-02 0:38 ` dpdklab
2024-03-02 0:39 ` dpdklab
2024-03-02 0:46 ` dpdklab
2024-03-02 0:46 ` dpdklab
2024-03-02 0:46 ` dpdklab
2024-03-02 0:55 ` dpdklab
2024-03-02 0:56 ` dpdklab
2024-03-02 0:56 ` dpdklab
2024-03-02 0:57 ` dpdklab
2024-03-02 0:58 ` dpdklab
2024-03-02 0:58 ` dpdklab
2024-03-02 0:59 ` dpdklab
2024-03-02 0:59 ` dpdklab
2024-03-02 1:00 ` dpdklab
2024-03-02 1:02 ` dpdklab
2024-03-02 1:03 ` dpdklab
2024-03-02 1:05 ` dpdklab
2024-03-02 1:07 ` dpdklab
2024-03-02 1:11 ` dpdklab
2024-03-02 1:12 ` dpdklab
2024-03-02 1:25 ` dpdklab
2024-03-02 2:34 ` |SUCCESS| pw137691-137761 [PATCH v2 71/71] examples: replace use of fixed size rte_memcpy qemudev
2024-03-02 2:38 ` qemudev
2024-03-02 3:51 ` |SUCCESS| pw137691-137761 [PATCH] [v2,71/71] examples: replace use o dpdklab
2024-03-03 1:05 ` dpdklab
2024-03-04 6:06 ` dpdklab
2024-03-05 22:17 ` dpdklab
2024-03-05 22:50 ` dpdklab
2024-03-05 23:22 ` 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=65e2623a.170a0220.ff040.84c2SMTPIN_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=lijuan.tu@intel.com \
--cc=qian.q.xu@intel.com \
--cc=stephen@networkplumber.org \
--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).