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| pw135904-135927 [PATCH] [v3,24/24] crypto/cnxk: add CPT SG
Date: Wed, 17 Jan 2024 18:46:50 -0800 (PST)	[thread overview]
Message-ID: <65a8911a.050a0220.772c9.b0a5SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Anoob Joseph <anoobj@marvell.com>
Date: Wednesday, January 17 2024 10:31:09 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:d4af9a82063e4c39568191eaa12955d3ca39581a

135904-135927 --> functional testing pass

Test environment and result as below:

Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 9.4
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


Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-18  2:46 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18  2:46 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-18 12:12 dpdklab
2024-01-18  6:48 dpdklab
2024-01-18  6:46 dpdklab
2024-01-18  6:44 dpdklab
2024-01-18  6:28 dpdklab
2024-01-18  5:45 dpdklab
2024-01-18  5:31 dpdklab
2024-01-18  5:10 dpdklab
2024-01-18  4:54 dpdklab
2024-01-18  4:45 dpdklab
2024-01-18  4:43 dpdklab
2024-01-18  4:41 dpdklab
2024-01-18  4:36 dpdklab
2024-01-18  4:35 dpdklab
2024-01-18  4:35 dpdklab
2024-01-18  4:35 dpdklab
2024-01-18  4:35 dpdklab
2024-01-18  4:32 dpdklab
2024-01-18  4:31 dpdklab
2024-01-18  4:31 dpdklab
2024-01-18  4:31 dpdklab
2024-01-18  4:31 dpdklab
2024-01-18  4:29 dpdklab
2024-01-18  4:28 dpdklab
2024-01-18  4:27 dpdklab
2024-01-18  4:27 dpdklab
2024-01-18  4:26 dpdklab
2024-01-18  4:26 dpdklab
2024-01-18  4:26 dpdklab
2024-01-18  4:23 dpdklab
2024-01-18  4:23 dpdklab
2024-01-18  4:22 dpdklab
2024-01-18  4:22 dpdklab
2024-01-18  4:17 dpdklab
2024-01-18  4:17 dpdklab
2024-01-18  4:16 dpdklab
2024-01-18  4:15 dpdklab
2024-01-18  4:13 dpdklab
2024-01-18  4:13 dpdklab
2024-01-18  3:56 dpdklab
2024-01-18  3:55 dpdklab
2024-01-18  3:54 dpdklab
2024-01-18  3:53 dpdklab
2024-01-18  3:52 dpdklab
2024-01-18  3:51 dpdklab
2024-01-18  3:50 dpdklab
2024-01-18  3:49 dpdklab
2024-01-18  3:46 dpdklab
2024-01-18  3:43 dpdklab
2024-01-18  3:43 dpdklab
2024-01-18  3:42 dpdklab
2024-01-18  3:41 dpdklab
2024-01-18  3:41 dpdklab
2024-01-18  3:34 dpdklab
2024-01-18  3:33 dpdklab
2024-01-18  3:12 dpdklab
2024-01-18  3:06 dpdklab
2024-01-18  3:06 dpdklab
2024-01-18  3:05 dpdklab
2024-01-18  2:55 dpdklab
2024-01-18  2:54 dpdklab
2024-01-18  2:54 dpdklab
2024-01-18  2:54 dpdklab
2024-01-18  2:51 dpdklab
2024-01-18  2:50 dpdklab
2024-01-18  2:50 dpdklab
2024-01-18  2:47 dpdklab
2024-01-18  2:45 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=65a8911a.050a0220.772c9.b0a5SMTPIN_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).