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| pw93094 [PATCH] [v2] raw/ioat: fix parameter shadow warning
Date: Mon, 10 May 2021 09:26:12 -0400 (EDT)	[thread overview]
Message-ID: <20210510132612.6ECF330553@noxus.dpdklab.iol.unh.edu> (raw)

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

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

_Functional Testing PASS_

Submitter: Kevin Laatz <kevin.laatz@intel.com>
Date: Monday, May 10 2021 12:55:14 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:627c5b41bb14a1afbd1489b0fc4b8224532a823d

93094 --> 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 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/5


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2021-05-10 13:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-10 13:26 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-05-11 11:20 dpdklab
2021-05-11  8:40 dpdklab
2021-05-10 18:19 dpdklab
2021-05-10 18:05 dpdklab
2021-05-10 17:53 dpdklab
2021-05-10 13:34 dpdklab
2021-05-10 13:32 dpdklab
2021-05-10 13:30 dpdklab
     [not found] <20210510125514.12914-1-kevin.laatz@intel.com>
2021-05-10 12:57 ` [dpdk-test-report] |SUCCESS| pw93094 [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=20210510132612.6ECF330553@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).