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| pw130048 [PATCH] [v3] doc: update QAT cryptodev guide to r
Date: Thu, 10 Aug 2023 07:38:34 -0700 (PDT)	[thread overview]
Message-ID: <64d4f66a.170a0220.e4ae0.15aaSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Dharmik Thakkar <dharmikjayesh.thakkar@arm.com>
Date: Wednesday, August 09 2023 15:38:14 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:70b6941e4e22d67bc10495d1638234a7e974f582

130048 --> 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/27266/

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 14:38 UTC|newest]

Thread overview: 103+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-10 14:38 dpdklab [this message]
2023-08-10 14:40 dpdklab
2023-08-10 14:58 dpdklab
2023-08-10 14:58 dpdklab
2023-08-10 15:01 dpdklab
2023-08-10 15:11 dpdklab
2023-08-10 15:12 dpdklab
2023-08-10 15:13 dpdklab
2023-08-10 15:13 dpdklab
2023-08-10 15:13 dpdklab
2023-08-10 15:13 dpdklab
2023-08-10 15:13 dpdklab
2023-08-10 15:16 dpdklab
2023-08-10 15:16 dpdklab
2023-08-10 15:20 dpdklab
2023-08-10 15:21 dpdklab
2023-08-10 15:25 dpdklab
2023-08-10 15:27 dpdklab
2023-08-10 15:27 dpdklab
2023-08-10 15:31 dpdklab
2023-08-10 15:38 dpdklab
2023-08-10 15:40 dpdklab
2023-08-10 15:41 dpdklab
2023-08-10 15:42 dpdklab
2023-08-10 15:43 dpdklab
2023-08-10 15:52 dpdklab
2023-08-10 15:56 dpdklab
2023-08-10 16:01 dpdklab
2023-08-10 16:01 dpdklab
2023-08-10 16:05 dpdklab
2023-08-10 16:05 dpdklab
2023-08-10 16:05 dpdklab
2023-08-10 16:08 dpdklab
2023-08-10 16:09 dpdklab
2023-08-10 16:09 dpdklab
2023-08-10 16:10 dpdklab
2023-08-10 16:19 dpdklab
2023-08-10 16:20 dpdklab
2023-08-10 16:20 dpdklab
2023-08-10 16:46 dpdklab
2023-08-10 16:50 dpdklab
2023-08-11  2:08 dpdklab
2023-08-11  2:39 dpdklab
2023-08-11  2:40 dpdklab
2023-08-11  2:42 dpdklab
2023-08-11  2:44 dpdklab
2023-08-11  2:46 dpdklab
2023-08-11  2:47 dpdklab
2023-08-11  2:47 dpdklab
2023-08-11  2:47 dpdklab
2023-08-11  2:48 dpdklab
2023-08-11  2:51 dpdklab
2023-08-11  2:52 dpdklab
2023-08-11  2:52 dpdklab
2023-08-11  2:52 dpdklab
2023-08-11  2:53 dpdklab
2023-08-11  2:53 dpdklab
2023-08-11  2:53 dpdklab
2023-08-11  2:54 dpdklab
2023-08-11  2:55 dpdklab
2023-08-11  3:39 dpdklab
2023-08-11  3:54 dpdklab
2023-08-11  3:58 dpdklab
2023-08-11  4:01 dpdklab
2023-08-11  4:05 dpdklab
2023-08-11  4:06 dpdklab
2023-08-11  4:08 dpdklab
2023-08-11  4:09 dpdklab
2023-08-11  4:09 dpdklab
2023-08-11  4:20 dpdklab
2023-08-11  4:22 dpdklab
2023-08-11  4:35 dpdklab
2023-08-11  4:35 dpdklab
2023-08-11  4:36 dpdklab
2023-08-11  4:36 dpdklab
2023-08-11  4:36 dpdklab
2023-08-11  4:38 dpdklab
2023-08-11  4:40 dpdklab
2023-08-11  4:44 dpdklab
2023-08-11  4:56 dpdklab
2023-08-11  5:06 dpdklab
2023-08-11  8:22 dpdklab
2023-08-11 21:14 dpdklab
2023-08-11 21:19 dpdklab
2023-08-11 21:26 dpdklab
2023-08-11 21:26 dpdklab
2023-08-11 21:27 dpdklab
2023-08-11 21:30 dpdklab
2023-08-11 21:31 dpdklab
2023-08-11 21:33 dpdklab
2023-08-11 21:34 dpdklab
2023-08-11 22:47 dpdklab
2023-08-13 19:16 dpdklab
2023-08-13 22:05 dpdklab
2023-08-14  1:43 dpdklab
2023-08-14  1:43 dpdklab
2023-08-14  1:44 dpdklab
2023-08-14  1:46 dpdklab
2023-08-14  1:46 dpdklab
2023-08-14  1:46 dpdklab
2023-08-14  1:47 dpdklab
2023-08-14  1:52 dpdklab
2023-08-14  2:00 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=64d4f66a.170a0220.e4ae0.15aaSMTPIN_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).