From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw108860 [PATCH] [v4] net/ixgbe: retry SFP ID read to handle misbehaving SFPs
Date: Fri, 25 Mar 2022 06:25:10 -0400 (EDT) [thread overview]
Message-ID: <20220325102510.04C546D45F@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 780 bytes --]
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/108860
_Functional Testing PASS_
Submitter: Jeff Daly <jeffd@silicom-usa.com>
Date: Friday, March 25 2022 09:54:13
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:1d5e58e9b6962cb00fc5c7369cbf4e3b932a9b8e
108860 --> functional testing pass
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/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/21569/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-03-25 10:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 10:25 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-25 12:31 dpdklab
2022-03-25 12:04 dpdklab
2022-03-25 11:43 dpdklab
2022-03-25 11:43 dpdklab
2022-03-25 11:28 dpdklab
2022-03-25 10:43 dpdklab
2022-03-25 10:38 dpdklab
2022-03-25 10:32 dpdklab
2022-03-25 10:31 dpdklab
2022-03-25 10:26 dpdklab
[not found] <20220325095414.12854-1-jeffd@silicom-usa.com>
2022-03-25 9:56 ` |SUCCESS| pw108860 [PATCH v4] " checkpatch
2022-03-25 11:59 ` 0-day Robot
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=20220325102510.04C546D45F@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).