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: |SUCCESS| pw130065-130070 [PATCH] [v1,6/6] crypto/cnxk: add SM2 supp
Date: Thu, 10 Aug 2023 03:05:19 -0700 (PDT)	[thread overview]
Message-ID: <64d4b65f.050a0220.63f3f.467fSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Date: Thursday, August 10 2023 09:35:28 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:70b6941e4e22d67bc10495d1638234a7e974f582

130065-130070 --> functional testing pass

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15.0-58-generic x86_64
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-08-10 10:05 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-10 10:05 dpdklab [this message]
2023-08-10 10:07 dpdklab
2023-08-10 10:08 dpdklab
2023-08-10 10:08 dpdklab
2023-08-10 10:12 dpdklab
2023-08-10 10:14 dpdklab
2023-08-11  0:50 dpdklab
2023-08-11  2:05 dpdklab
2023-08-11  2:05 dpdklab
2023-08-11  2:05 dpdklab
2023-08-11  2:05 dpdklab
2023-08-11  2:05 dpdklab
2023-08-11  2:06 dpdklab
2023-08-11  2:06 dpdklab
2023-08-11  2:07 dpdklab
2023-08-11  2:08 dpdklab
2023-08-11  2:09 dpdklab
2023-08-11  2:09 dpdklab
2023-08-11  2:10 dpdklab
2023-08-11  2:10 dpdklab
2023-08-11  2:10 dpdklab
2023-08-11  2:10 dpdklab
2023-08-11  2:10 dpdklab
2023-08-11  2:11 dpdklab
2023-08-11  2:11 dpdklab
2023-08-11  2:11 dpdklab
2023-08-11  2:12 dpdklab
2023-08-11  2:12 dpdklab
2023-08-11  2:13 dpdklab
2023-08-11  2:13 dpdklab
2023-08-11  2:13 dpdklab
2023-08-11  2:14 dpdklab
2023-08-11  2:23 dpdklab
2023-08-11  2:23 dpdklab
2023-08-11  2:25 dpdklab
2023-08-11  2:26 dpdklab
2023-08-11  2:28 dpdklab
2023-08-11  2:39 dpdklab
2023-08-11  2:40 dpdklab
2023-08-11  2:42 dpdklab
2023-08-11  2:43 dpdklab
2023-08-11  2:43 dpdklab
2023-08-11  2:45 dpdklab
2023-08-11  2:47 dpdklab
2023-08-11  2:52 dpdklab
2023-08-11  2:53 dpdklab
2023-08-11  2:54 dpdklab
2023-08-11  3:55 dpdklab
2023-08-11  7:41 dpdklab
2023-08-11 20:02 dpdklab
2023-08-11 20:04 dpdklab
2023-08-11 20:05 dpdklab
2023-08-11 20:05 dpdklab
2023-08-11 20:06 dpdklab
2023-08-11 20:26 dpdklab
2023-08-11 20:40 dpdklab
2023-08-11 21:21 dpdklab
2023-08-11 21:27 dpdklab
2023-08-11 21:32 dpdklab
2023-08-13 19:12 dpdklab
2023-08-13 21:42 dpdklab
2023-08-14  1:09 dpdklab
2023-08-14  1:09 dpdklab
2023-08-14  1:09 dpdklab
2023-08-14  1:12 dpdklab
2023-08-14  1:13 dpdklab
2023-08-14  1:13 dpdklab
2023-08-14  1:14 dpdklab
2023-08-14  1:17 dpdklab
2023-08-14  1:19 dpdklab
2023-08-14  1:20 dpdklab
2023-08-14  1:34 dpdklab
2023-08-14  1:57 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=64d4b65f.050a0220.63f3f.467fSMTPIN_ADDED_MISSING@mx.google.com \
    --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).