From: dpdklab@iol.unh.edu
To: Ajit Khaparde <ajit.khaparde@broadcom.com>,
Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw97766 [PATCH] net/ice: fix representor port segmentation fault
Date: Thu, 2 Sep 2021 08:11:11 -0400 (EDT) [thread overview]
Message-ID: <20210902121111.990B889060@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 793 bytes --]
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/97766
_Functional Testing PASS_
Submitter: Yu, DapengX <dapengx.yu@intel.com>
Date: Thursday, September 02 2021 09:44:08
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:eeedef704c11bd74c367d62838700bdb8e5b573f
97766 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04
Kernel: 4.15.0-65-generic
Compiler: gcc gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
NIC: Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/18502/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-09-02 12:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 12:11 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-09-04 17:16 dpdklab
2021-09-04 17:16 dpdklab
2021-09-04 17:16 dpdklab
2021-09-04 17:14 dpdklab
2021-09-04 17:13 dpdklab
2021-09-04 14:51 dpdklab
2021-09-02 12:34 dpdklab
2021-09-02 12:04 dpdklab
2021-09-02 11:59 dpdklab
2021-09-02 11:50 dpdklab
2021-09-02 11:36 dpdklab
2021-09-02 11:36 dpdklab
2021-09-02 11:32 dpdklab
2021-09-02 11:27 dpdklab
2021-09-02 11:20 dpdklab
2021-09-02 11:14 dpdklab
2021-09-02 11:10 dpdklab
2021-09-02 11:08 dpdklab
2021-09-02 11:05 dpdklab
2021-09-02 10:58 dpdklab
[not found] <20210902094408.1294361-1-dapengx.yu@intel.com>
2021-09-02 9:46 ` checkpatch
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=20210902121111.990B889060@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=ajit.khaparde@broadcom.com \
--cc=dpdk-test-reports@iol.unh.edu \
--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).