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| pw97312-97322 [PATCH] [v2, 11/11] crypto/dpaa2_sec: add error packet counters
Date: Wed, 25 Aug 2021 06:15:05 -0400 (EDT)	[thread overview]
Message-ID: <20210825101505.BF771B0FE@noxus.dpdklab.iol.unh.edu> (raw)

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

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

_Functional Testing PASS_

Submitter: Hemant Agrawal <hemant.agrawal@nxp.com>
Date: Wednesday, August 25 2021 08:18:37 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fdab8f2e17493192d555cd88cf28b06269174326

97312-97322 --> 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/18343/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2021-08-25 10:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-25 10:15 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-08-26  7:53 dpdklab
2021-08-25 22:54 dpdklab
2021-08-25 21:59 dpdklab
2021-08-25 11:54 dpdklab
2021-08-25 11:51 dpdklab
2021-08-25 11:28 dpdklab
2021-08-25 11:06 dpdklab
2021-08-25 10:51 dpdklab
2021-08-25 10:44 dpdklab
2021-08-25 10:43 dpdklab
2021-08-25 10:38 dpdklab
2021-08-25 10:34 dpdklab
2021-08-25 10:23 dpdklab
2021-08-25 10:07 dpdklab

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=20210825101505.BF771B0FE@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).