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| pw128781-128783 [PATCH] [v7,3/3] test/crypto: skip asym te
Date: Fri, 16 Jun 2023 07:50:11 -0700 (PDT)	[thread overview]
Message-ID: <648c76a3.920a0220.c367.0a4dSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Vikash Poddar <vikash.chandrax.poddar@intel.com>
Date: Friday, June 16 2023 14:00:53 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:7556a1a355fb377279508735f7afc1faf1d00158

128781-128783 --> functional testing pass

Test environment and result as below:

Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2


Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-06-16 14:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-16 14:50 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-21  6:40 dpdklab
2023-06-21  6:35 dpdklab
2023-06-20 17:47 dpdklab
2023-06-20 17:37 dpdklab
2023-06-20 17:29 dpdklab
2023-06-18 18:21 dpdklab
2023-06-17  7:15 dpdklab
2023-06-17  7:05 dpdklab
2023-06-17  7:02 dpdklab
2023-06-16 19:10 dpdklab
2023-06-16 18:40 dpdklab
2023-06-16 18:36 dpdklab
2023-06-16 18:30 dpdklab
2023-06-16 18:30 dpdklab
2023-06-16 14:44 dpdklab
2023-06-16 14:44 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=648c76a3.920a0220.c367.0a4dSMTPIN_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).