automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Ajit Khaparde <ajit.khaparde@broadcom.com>,
	Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw104006 [PATCH] test/crypto: skip plain text compare for null cipher OOP
Date: Tue,  9 Nov 2021 00:53:44 +0000 (UTC)	[thread overview]
Message-ID: <20211109005344.4DDF360099@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/104006

_Functional Testing PASS_

Submitter: Anoob Joseph <anoobj@marvell.com>
Date: Monday, November 08 2021 15:19:51 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fb73eb2fb1b8648513ab5d86ba7548d330d91b06

104006 --> functional testing pass

Test environment and result as below:

Ubuntu 20.04
Kernel: 4.15.0-65-generic
Compiler: gcc gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
NIC: Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2021-11-09  0:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-09  0:53 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-11-09  4:24 dpdklab
2021-11-09  4:22 dpdklab
2021-11-09  4:17 dpdklab
2021-11-09  3:09 dpdklab
2021-11-09  2:02 dpdklab
2021-11-09  1:14 dpdklab
2021-11-09  1:07 dpdklab
2021-11-09  1:05 dpdklab
2021-11-09  0:14 dpdklab
     [not found] <1636384791-157-1-git-send-email-anoobj@marvell.com>
2021-11-08 15:20 ` 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=20211109005344.4DDF360099@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=ajit.khaparde@broadcom.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).