automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw86708 [PATCH] ethdev: rename FEC API parameters
Date: Fri, 15 Jan 2021 12:20:36 -0500 (EST)	[thread overview]
Message-ID: <20210115172036.8FE7988E5F@noxus.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 787 bytes --]

Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/86708

_Functional Testing PASS_

Submitter: Ferruh Yigit <ferruh.yigit@intel.com>
Date: Friday, January 15 2021 15:52:32 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:8e266978e4e75d3c444b443c1fdab485b2990ad4

86708 --> functional testing pass

Test environment and result as below:

Ubuntu 18.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


To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/15228/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2021-01-15 17:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-15 17:20 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-01-19  7:07 dpdklab
2021-01-19  5:38 dpdklab
2021-01-18  4:06 dpdklab
2021-01-18  3:16 dpdklab
2021-01-17  0:21 dpdklab
2021-01-16 23:30 dpdklab
2021-01-15 18:05 dpdklab
2021-01-15 17:51 dpdklab
2021-01-15 17:48 dpdklab
2021-01-15 17:34 dpdklab
2021-01-15 17:17 dpdklab
     [not found] <20210115155232.1406688-1-ferruh.yigit@intel.com>
2021-01-15 15:52 ` 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=20210115172036.8FE7988E5F@noxus.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --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).