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| pw138118 [PATCH] app/test: fix rsa tests in qat suite
Date: Fri, 08 Mar 2024 04:39:21 -0800 (PST)	[thread overview]
Message-ID: <65eb06f9.920a0220.e34de.7b2eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240308081750.5157-1-arkadiuszx.kusztal@intel.com>

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

_Functional Testing PASS_

Submitter: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Date: Friday, March 08 2024 08:17:50 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:4877d26a37d3bb515fc714b260066c0cac1985cf

138118 --> functional testing pass

Test environment and result as below:

Ubuntu 22.04 ARM
Kernel: 5.15.82
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-82
Compiler: gcc 11.4.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/1


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-08 12:39 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240308081750.5157-1-arkadiuszx.kusztal@intel.com>
2024-03-08  7:55 ` qemudev
2024-03-08  7:59 ` qemudev
2024-03-08  8:19 ` checkpatch
2024-03-08  9:24 ` 0-day Robot
2024-03-08  9:29 ` dpdklab
2024-03-08  9:29 ` dpdklab
2024-03-08  9:31 ` dpdklab
2024-03-08  9:40 ` dpdklab
2024-03-08  9:59 ` dpdklab
2024-03-08  9:59 ` dpdklab
2024-03-08 10:00 ` dpdklab
2024-03-08 10:00 ` dpdklab
2024-03-08 10:01 ` dpdklab
2024-03-08 10:01 ` dpdklab
2024-03-08 10:01 ` dpdklab
2024-03-08 10:02 ` dpdklab
2024-03-08 10:02 ` dpdklab
2024-03-08 10:03 ` dpdklab
2024-03-08 10:03 ` dpdklab
2024-03-08 10:03 ` dpdklab
2024-03-08 10:04 ` dpdklab
2024-03-08 10:04 ` dpdklab
2024-03-08 10:04 ` dpdklab
2024-03-08 10:04 ` dpdklab
2024-03-08 10:05 ` dpdklab
2024-03-08 10:05 ` dpdklab
2024-03-08 10:05 ` dpdklab
2024-03-08 10:05 ` dpdklab
2024-03-08 10:05 ` dpdklab
2024-03-08 10:06 ` dpdklab
2024-03-08 10:07 ` dpdklab
2024-03-08 10:08 ` dpdklab
2024-03-08 10:08 ` dpdklab
2024-03-08 10:08 ` dpdklab
2024-03-08 10:09 ` dpdklab
2024-03-08 10:09 ` dpdklab
2024-03-08 10:09 ` dpdklab
2024-03-08 10:09 ` dpdklab
2024-03-08 10:09 ` dpdklab
2024-03-08 10:09 ` dpdklab
2024-03-08 10:10 ` dpdklab
2024-03-08 10:10 ` dpdklab
2024-03-08 10:10 ` dpdklab
2024-03-08 10:10 ` dpdklab
2024-03-08 10:11 ` dpdklab
2024-03-08 10:11 ` dpdklab
2024-03-08 10:12 ` dpdklab
2024-03-08 10:12 ` dpdklab
2024-03-08 10:12 ` dpdklab
2024-03-08 10:12 ` dpdklab
2024-03-08 10:12 ` dpdklab
2024-03-08 10:13 ` dpdklab
2024-03-08 10:13 ` dpdklab
2024-03-08 10:13 ` dpdklab
2024-03-08 10:13 ` dpdklab
2024-03-08 10:14 ` dpdklab
2024-03-08 10:14 ` dpdklab
2024-03-08 10:15 ` dpdklab
2024-03-08 10:19 ` dpdklab
2024-03-08 10:19 ` dpdklab
2024-03-08 10:19 ` dpdklab
2024-03-08 10:20 ` dpdklab
2024-03-08 10:23 ` dpdklab
2024-03-08 10:28 ` dpdklab
2024-03-08 10:29 ` dpdklab
2024-03-08 10:32 ` dpdklab
2024-03-08 10:36 ` dpdklab
2024-03-08 11:38 ` dpdklab
2024-03-08 12:05 ` dpdklab
2024-03-08 12:37 ` dpdklab
2024-03-08 12:39 ` dpdklab [this message]
2024-03-08 12:41 ` dpdklab
2024-03-08 12:44 ` dpdklab
2024-03-12 23:07 ` dpdklab
2024-03-12 23:36 ` 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=65eb06f9.920a0220.e34de.7b2eSMTPIN_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).