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,
	David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw124814 [PATCH] [v2] crypto/ccp: bug fixes for ccp device probe flow
Date: Mon,  6 Mar 2023 14:45:52 +0000 (UTC)	[thread overview]
Message-ID: <20230306144552.4366060095@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

_Functional Testing PASS_

Submitter: Sunil Uttarwar <sunilprakashrao.uttarwar@amd.com>
Date: Monday, March 06 2023 12:58:37 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:4ef69b2877a24ddb89afaf4bb6f4e73bb52a605b

124814 --> functional testing pass

Test environment and result as below:

Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-137-generic aarch64
Compiler: gcc 9.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-03-06 14:45 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-06 14:45 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-06 17:15 dpdklab
2023-03-06 17:15 dpdklab
2023-03-06 17:14 dpdklab
2023-03-06 17:11 dpdklab
2023-03-06 17:07 dpdklab
2023-03-06 16:42 dpdklab
2023-03-06 16:40 dpdklab
2023-03-06 16:38 dpdklab
2023-03-06 16:33 dpdklab
2023-03-06 16:28 dpdklab
2023-03-06 16:27 dpdklab
2023-03-06 16:26 dpdklab
2023-03-06 16:19 dpdklab
2023-03-06 16:18 dpdklab
2023-03-06 16:17 dpdklab
2023-03-06 16:16 dpdklab
2023-03-06 16:12 dpdklab
2023-03-06 16:04 dpdklab
2023-03-06 15:51 dpdklab
2023-03-06 15:37 dpdklab
2023-03-06 15:32 dpdklab
2023-03-06 15:31 dpdklab
2023-03-06 15:27 dpdklab
2023-03-06 15:26 dpdklab
2023-03-06 15:16 dpdklab
2023-03-06 15:11 dpdklab
2023-03-06 15:08 dpdklab
2023-03-06 15:01 dpdklab
2023-03-06 14:56 dpdklab
2023-03-06 14:48 dpdklab
2023-03-06 14:45 dpdklab
2023-03-06 14:41 dpdklab
2023-03-06 14:37 dpdklab
2023-03-06 14:37 dpdklab
2023-03-06 14:36 dpdklab
2023-03-06 14:35 dpdklab
2023-03-06 14:34 dpdklab
2023-03-06 14:32 dpdklab
2023-03-06 14:30 dpdklab
2023-03-06 14:24 dpdklab
2023-03-06 14:24 dpdklab
2023-03-06 14:22 dpdklab
2023-03-06 14:20 dpdklab
2023-03-06 14:18 dpdklab
2023-03-06 14:16 dpdklab
2023-03-06 14:15 dpdklab
2023-03-06 14:11 dpdklab
2023-03-06 14:07 dpdklab
2023-03-06 14:07 dpdklab
     [not found] <20230306125837.94671-1-sunilprakashrao.uttarwar@amd.com>
2023-03-06 12:48 ` |SUCCESS| pw124814 [PATCH v2] " qemudev
2023-03-06 12:52 ` qemudev
2023-03-06 12:59 ` checkpatch
2023-03-06 14:59 ` 0-day Robot

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=20230306144552.4366060095@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).