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| pw85725 [PATCH] [v3] app/testpmd: increase array for fetching supported FEC caps
Date: Thu, 24 Dec 2020 07:48:39 -0500 (EST)	[thread overview]
Message-ID: <20201224124839.4BB8C30576@noxus.dpdklab.iol.unh.edu> (raw)

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

Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/85725

_Testing PASS_

Submitter: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
Date: Thursday, December 24 2020 11:18:49 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:9d620630ea30386d7fc2ff192656a9051b6dc6b5

85725 --> testing pass

Test environment and result as below:

+--------------+----------+
| Environment  | abi_test |
+==============+==========+
| Ubuntu 18.04 | PASS     |
+--------------+----------+

Ubuntu 18.04
	Kernel: 4.15.0-generic
	Compiler: gcc 7.5

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2020-12-24 12:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-24 12:48 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-12-24 13:33 dpdklab
2020-12-24 13:20 dpdklab
2020-12-24 13:04 dpdklab
2020-12-24 12:57 dpdklab
2020-12-24 12:45 dpdklab
2020-12-24 12:41 dpdklab
2020-12-24 12:37 dpdklab
2020-12-24 12:31 dpdklab
2020-12-24 12:23 dpdklab
2020-12-24 12:22 dpdklab
2020-12-24 12:16 dpdklab
     [not found] <1608808729-3768-1-git-send-email-rahul.lakkireddy@chelsio.com>
2020-12-24 11:37 ` [dpdk-test-report] |SUCCESS| pw85725 [PATCH v3] " 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=20201224124839.4BB8C30576@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).