automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw93264 [PATCH] [v2] devtools: add acronyms in dictionary for commit checks
Date: Sun, 16 May 2021 17:33:16 -0400 (EDT)	[thread overview]
Message-ID: <20210516213316.83F313155@noxus.dpdklab.iol.unh.edu> (raw)

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

Test-Label: iol-mellanox-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/93264

_Functional Testing PASS_

Submitter: Ferruh Yigit <ferruh.yigit@intel.com>
Date: Friday, May 14 2021 09:03:08 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:7989b7e7da9be588563c809264c9347a35319969

93264 --> functional testing pass

Test environment and result as below:

Ubuntu 18.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Mellanox ConnectX-4 Lx 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/5


Ubuntu 18.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Mellanox ConnectX-4 Lx 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/5


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2021-05-16 21:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-16 21:33 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-05-18  8:54 dpdklab
2021-05-18  6:38 dpdklab
2021-05-18  5:59 dpdklab
2021-05-16 21:45 dpdklab
2021-05-16 20:52 dpdklab
2021-05-16 20:40 dpdklab
2021-05-16 20:27 dpdklab
2021-05-14  9:56 dpdklab
2021-05-14  9:54 dpdklab
2021-05-14  9:40 dpdklab
     [not found] <20210514090308.2905151-1-ferruh.yigit@intel.com>
2021-05-14  9:03 ` [dpdk-test-report] |SUCCESS| pw93264 [PATCH v2] " 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=20210516213316.83F313155@noxus.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=alialnu@nvidia.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).