From: dpdklab@iol.unh.edu
To: 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>,
Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dpdk-test-reports@iol.unh.edu,
Rahul Gupta <rahulgupt@linux.microsoft.com>
Subject: |FAILURE| pw135939 [PATCH] [v2] eal: refactor rte_eal_init into sub-
Date: Wed, 17 Jan 2024 16:43:19 -0800 (PST) [thread overview]
Message-ID: <65a87427.050a0220.6f1a0.8dd9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: FAILURE
http://dpdk.org/patch/135939
_Functional Testing issues_
Submitter: Rahul Gupta <rahulgupt@linux.microsoft.com>
Date: Wednesday, January 17 2024 19:25:02
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:d4af9a82063e4c39568191eaa12955d3ca39581a
135939 --> functional testing fail
Test environment and result as below:
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
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: 1/3
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: 1/3
Failed Tests:
- unit_tests_mbuf
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:
- unit_tests_mbuf
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28888/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-18 0:43 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 0:43 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-17 23:07 dpdklab
2024-01-17 22:56 dpdklab
2024-01-17 22:54 dpdklab
2024-01-17 22:47 dpdklab
2024-01-17 22:43 dpdklab
2024-01-17 22:42 dpdklab
2024-01-17 22:42 dpdklab
2024-01-17 22:41 dpdklab
2024-01-17 22:41 dpdklab
2024-01-17 22:39 dpdklab
2024-01-17 22:38 dpdklab
2024-01-17 22:36 dpdklab
2024-01-17 22:11 dpdklab
2024-01-17 22:06 dpdklab
2024-01-17 22:00 dpdklab
2024-01-17 21:59 dpdklab
2024-01-17 21:56 dpdklab
2024-01-17 21:54 dpdklab
2024-01-17 21:54 dpdklab
2024-01-17 21:53 dpdklab
2024-01-17 21:53 dpdklab
2024-01-17 21:52 dpdklab
2024-01-17 21:51 dpdklab
2024-01-17 21:51 dpdklab
2024-01-17 21:50 dpdklab
2024-01-17 21:50 dpdklab
2024-01-17 21:49 dpdklab
2024-01-17 21:33 dpdklab
2024-01-17 21:33 dpdklab
2024-01-17 21:32 dpdklab
2024-01-17 21:27 dpdklab
2024-01-17 21:27 dpdklab
2024-01-17 21:24 dpdklab
2024-01-17 21:18 dpdklab
2024-01-17 21:17 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=65a87427.050a0220.6f1a0.8dd9SMTPIN_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=rahulgupt@linux.microsoft.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).