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| pw131729-131740 [PATCH] [v2,13/13] crypto/dpaax_sec: enabl
Date: Wed, 20 Sep 2023 10:44:23 -0700 (PDT)	[thread overview]
Message-ID: <650b2f77.6b0a0220.50dfd.99e9SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Hemant Agrawal <hemant.agrawal@nxp.com>
Date: Wednesday, September 20 2023 13:34:03 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:31e60e81f025e9fffa69b68bffe5cfaa22d5c098

131729-131740 --> 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/27671/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-09-20 17:44 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-20 17:44 dpdklab [this message]
2023-09-20 17:44 dpdklab
2023-09-20 17:47 dpdklab
2023-09-20 18:05 dpdklab
2023-09-20 18:05 dpdklab
2023-09-20 18:05 dpdklab
2023-09-20 18:06 dpdklab
2023-09-20 18:06 dpdklab
2023-09-20 18:06 dpdklab
2023-09-20 18:06 dpdklab
2023-09-20 18:07 dpdklab
2023-09-20 18:07 dpdklab
2023-09-20 18:07 dpdklab
2023-09-20 18:08 dpdklab
2023-09-20 18:08 dpdklab
2023-09-20 18:08 dpdklab
2023-09-20 18:09 dpdklab
2023-09-20 18:09 dpdklab
2023-09-20 18:09 dpdklab
2023-09-20 18:10 dpdklab
2023-09-20 18:11 dpdklab
2023-09-20 18:22 dpdklab
2023-09-20 18:22 dpdklab
2023-09-20 18:22 dpdklab
2023-09-20 18:22 dpdklab
2023-09-20 18:23 dpdklab
2023-09-20 18:24 dpdklab
2023-09-20 18:25 dpdklab
2023-09-20 18:43 dpdklab
2023-09-20 18:46 dpdklab
2023-09-20 19:19 dpdklab
2023-09-20 19:25 dpdklab
2023-09-20 19:56 dpdklab
2023-09-20 20:04 dpdklab
2023-09-20 20:08 dpdklab
2023-09-20 20:08 dpdklab
2023-09-20 20:11 dpdklab
2023-09-20 20:12 dpdklab
2023-09-20 20:38 dpdklab
2023-09-20 21:49 dpdklab
2023-09-21 16:59 dpdklab
2023-09-21 17:11 dpdklab
2023-09-21 17:15 dpdklab
2023-09-21 17:20 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=650b2f77.6b0a0220.50dfd.99e9SMTPIN_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).