From: dpdklab@iol.unh.edu
To: Lijuan Tu <lijuan.tu@intel.com>,
Test Report <test-report@dpdk.org>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Georgii Tkachuk <georgii.tkachuk@intel.com>,
Qian Xu <qian.q.xu@intel.com>
Cc: dpdk-test-reports@iol.unh.edu, Wenwu Ma <wenwux.ma@intel.com>
Subject: |FAILURE| pw137650 [PATCH] net/ice: fix null pointer dereferences
Date: Fri, 01 Mar 2024 12:47:39 -0800 (PST) [thread overview]
Message-ID: <65e23eeb.050a0220.6835.8c6fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240301052029.543989-1-wenwux.ma@intel.com>
Test-Label: iol-intel-Functional
Test-Status: FAILURE
http://dpdk.org/patch/137650
_Functional Testing issues_
Submitter: Wenwu Ma <wenwux.ma@intel.com>
Date: Friday, March 01 2024 05:20:29
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3408b132b31906fe1ed28d6b2009b98202e1cff0
137650 --> 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 82599ES 10000 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 XL710-QDA2 40000 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/29358/
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 20:47 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240301052029.543989-1-wenwux.ma@intel.com>
2024-03-01 5:34 ` |SUCCESS| " checkpatch
2024-03-01 6:25 ` 0-day Robot
2024-03-01 18:27 ` dpdklab
2024-03-01 18:28 ` dpdklab
2024-03-01 18:29 ` dpdklab
2024-03-01 18:36 ` dpdklab
2024-03-01 18:37 ` dpdklab
2024-03-01 18:38 ` dpdklab
2024-03-01 18:45 ` dpdklab
2024-03-01 18:45 ` dpdklab
2024-03-01 18:54 ` dpdklab
2024-03-01 18:56 ` dpdklab
2024-03-01 18:57 ` dpdklab
2024-03-01 18:57 ` dpdklab
2024-03-01 19:03 ` dpdklab
2024-03-01 19:10 ` dpdklab
2024-03-01 19:13 ` dpdklab
2024-03-01 20:21 ` dpdklab
2024-03-01 20:47 ` dpdklab [this message]
2024-03-01 21:14 ` dpdklab
2024-03-01 21:34 ` dpdklab
2024-03-01 21:35 ` dpdklab
2024-03-01 21:35 ` dpdklab
2024-03-01 21:36 ` dpdklab
2024-03-01 21:36 ` dpdklab
2024-03-01 21:37 ` dpdklab
2024-03-01 21:38 ` dpdklab
2024-03-01 21:43 ` dpdklab
2024-03-01 21:43 ` dpdklab
2024-03-01 21:43 ` dpdklab
2024-03-01 21:43 ` dpdklab
2024-03-01 21:43 ` dpdklab
2024-03-01 21:45 ` dpdklab
2024-03-01 21:46 ` dpdklab
2024-03-01 21:47 ` dpdklab
2024-03-01 21:47 ` dpdklab
2024-03-01 21:49 ` dpdklab
2024-03-01 21:50 ` dpdklab
2024-03-01 21:50 ` dpdklab
2024-03-01 21:52 ` dpdklab
2024-03-01 21:53 ` dpdklab
2024-03-01 21:54 ` dpdklab
2024-03-01 21:55 ` dpdklab
2024-03-01 22:02 ` dpdklab
2024-03-01 22:02 ` dpdklab
2024-03-01 22:02 ` dpdklab
2024-03-01 22:03 ` dpdklab
2024-03-01 22:14 ` dpdklab
2024-03-01 22:15 ` dpdklab
2024-03-01 22:16 ` dpdklab
2024-03-01 22:16 ` dpdklab
2024-03-01 22:17 ` |FAILURE| " dpdklab
2024-03-01 22:18 ` |SUCCESS| " dpdklab
2024-03-01 22:18 ` dpdklab
2024-03-01 22:19 ` dpdklab
2024-03-01 22:21 ` dpdklab
2024-03-01 22:22 ` dpdklab
2024-03-01 22:23 ` dpdklab
2024-03-01 22:26 ` dpdklab
2024-03-01 22:31 ` dpdklab
2024-03-01 22:32 ` dpdklab
2024-03-01 22:34 ` dpdklab
2024-03-01 23:18 ` dpdklab
2024-03-01 23:25 ` dpdklab
2024-03-01 23:26 ` dpdklab
2024-03-01 23:36 ` dpdklab
2024-03-02 0:46 ` dpdklab
2024-03-02 1:00 ` dpdklab
2024-03-02 2:55 ` dpdklab
2024-03-02 6:44 ` qemudev
2024-03-02 6:49 ` qemudev
2024-03-02 23:24 ` dpdklab
2024-03-05 16: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=65e23eeb.050a0220.6835.8c6fSMTPIN_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=test-report@dpdk.org \
--cc=wenwux.ma@intel.com \
/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).