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| pw126828-126829 [PATCH] [2/2] test/crypto: specify correct parameters with null algos
Date: Fri, 12 May 2023 17:02:44 -0700 (PDT)	[thread overview]
Message-ID: <645ed3a4.050a0220.c47cb.245eSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Anoob Joseph <anoobj@marvell.com>
Date: Friday, May 12 2023 05:33:53 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:d03446724972d2a1bb645ce7f3e64f5ef0203d61

126828-126829 --> 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


Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-148-generic aarch64
Compiler: gcc 9.4
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-05-13  0:02 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-13  0:02 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-13  0:17 dpdklab
2023-05-13  0:08 dpdklab
2023-05-12 23:57 dpdklab
2023-05-12 23:53 dpdklab
2023-05-12 17:11 dpdklab
2023-05-12 17:11 dpdklab
2023-05-12 17:07 dpdklab
2023-05-12 17:01 dpdklab
2023-05-12 16:32 dpdklab
2023-05-12 16:23 dpdklab
2023-05-12 16:13 dpdklab
2023-05-12 16:11 dpdklab
2023-05-12 16:08 dpdklab
2023-05-12 16:01 dpdklab
2023-05-12 15:53 dpdklab
2023-05-12 15:52 dpdklab
2023-05-12 15:51 dpdklab
2023-05-12 15:46 dpdklab
2023-05-12 15:41 dpdklab
2023-05-12 15:37 dpdklab
2023-05-12 15:34 dpdklab
2023-05-12 15:14 dpdklab
2023-05-12 14:54 dpdklab
2023-05-12 14:50 dpdklab
2023-05-12 14:38 dpdklab
2023-05-12 14:37 dpdklab
2023-05-12 14:36 dpdklab
2023-05-12 14:34 dpdklab
2023-05-12 14:29 dpdklab
     [not found] <20230512053353.68-2-anoobj@marvell.com>
2023-05-12  5:26 ` |SUCCESS| pw126828-126829 [PATCH 2/2] " qemudev
2023-05-12  5:30 ` qemudev

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=645ed3a4.050a0220.c47cb.245eSMTPIN_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).