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| pw103443-103444 [PATCH] [2/2] net/txgbe: fix link process in KR mode
Date: Tue, 2 Nov 2021 14:45:13 +0000 (UTC) [thread overview]
Message-ID: <20211102144513.81EA860099@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 801 bytes --]
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/103444
_Functional Testing PASS_
Submitter: Jiawen Wu <jiawenwu@trustnetic.com>
Date: Tuesday, November 02 2021 08:10:26
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:b2be63b55ab086c52c082d5c0b2b01fffbc48326
103443-103444 --> 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/19910/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-11-02 14:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 14:45 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-03 6:31 dpdklab
2021-11-03 0:03 dpdklab
2021-11-02 20:04 dpdklab
2021-11-02 19:51 dpdklab
2021-11-02 19:47 dpdklab
2021-11-02 19:14 dpdklab
2021-11-02 18:56 dpdklab
2021-11-02 17:07 dpdklab
2021-11-02 15:45 dpdklab
2021-11-02 15:27 dpdklab
2021-11-02 15:26 dpdklab
2021-11-02 15:22 dpdklab
2021-11-02 15:17 dpdklab
2021-11-02 15:10 dpdklab
2021-11-02 15:05 dpdklab
2021-11-02 15:04 dpdklab
2021-11-02 14:59 dpdklab
2021-11-02 14:57 dpdklab
2021-11-02 13:56 dpdklab
2021-11-02 13:43 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=20211102144513.81EA860099@dpdk-ubuntu.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).