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, Akhil Goyal <gakhil@marvell.com>
Subject: |SUCCESS| [GIT MASTER] 1ee6738c308b8b3cf230644187394f13ca6ec36f
Date: Thu, 18 Jan 2024 07:56:23 -0800 (PST)	[thread overview]
Message-ID: <65a94a27.050a0220.f4a58.1df5SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Functional Testing PASS_

Branch: dpdk-next-crypto

1ee6738c308b8b3cf230644187394f13ca6ec36f --> functional testing pass

Test environment and result as below:

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


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


To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/27715/

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 15:56 UTC|newest]

Thread overview: 114+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18 15:56 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-19 18:36 dpdklab
2024-01-18 23:04 dpdklab
2024-01-18 22:30 dpdklab
2024-01-18 19:53 dpdklab
2024-01-18 18:18 dpdklab
2024-01-18 17:43 dpdklab
2024-01-18 17:41 dpdklab
2024-01-18 17:40 dpdklab
2024-01-18 17:29 dpdklab
2024-01-18 17:28 dpdklab
2024-01-18 17:27 dpdklab
2024-01-18 17:27 dpdklab
2024-01-18 17:24 dpdklab
2024-01-18 17:23 dpdklab
2024-01-18 17:23 dpdklab
2024-01-18 17:20 dpdklab
2024-01-18 17:16 dpdklab
2024-01-18 17:16 dpdklab
2024-01-18 17:15 dpdklab
2024-01-18 17:14 dpdklab
2024-01-18 17:14 dpdklab
2024-01-18 17:14 dpdklab
2024-01-18 17:14 dpdklab
2024-01-18 17:13 dpdklab
2024-01-18 17:13 dpdklab
2024-01-18 17:12 dpdklab
2024-01-18 17:12 dpdklab
2024-01-18 17:12 dpdklab
2024-01-18 17:12 dpdklab
2024-01-18 17:11 dpdklab
2024-01-18 17:09 dpdklab
2024-01-18 17:09 dpdklab
2024-01-18 17:09 dpdklab
2024-01-18 17:08 dpdklab
2024-01-18 17:07 dpdklab
2024-01-18 17:07 dpdklab
2024-01-18 17:07 dpdklab
2024-01-18 17:06 dpdklab
2024-01-18 17:05 dpdklab
2024-01-18 17:04 dpdklab
2024-01-18 17:02 dpdklab
2024-01-18 16:51 dpdklab
2024-01-18 16:45 dpdklab
2024-01-18 16:45 dpdklab
2024-01-18 16:30 dpdklab
2024-01-18 16:29 dpdklab
2024-01-18 16:17 dpdklab
2024-01-18 16:05 dpdklab
2024-01-18 16:05 dpdklab
2024-01-18 16:04 dpdklab
2024-01-18 16:03 dpdklab
2024-01-18 16:01 dpdklab
2024-01-18 16:00 dpdklab
2024-01-18 15:59 dpdklab
2024-01-18 15:58 dpdklab
2024-01-18 15:55 dpdklab
2024-01-18 15:47 dpdklab
2024-01-09 23:39 dpdklab
2024-01-09 21:47 dpdklab
2024-01-09 21:29 dpdklab
2024-01-09 21:21 dpdklab
2024-01-09 21:20 dpdklab
2024-01-09 21:20 dpdklab
2024-01-09 21:20 dpdklab
2024-01-09 21:19 dpdklab
2024-01-09 21:18 dpdklab
2024-01-09 21:17 dpdklab
2024-01-09 21:17 dpdklab
2024-01-09 21:17 dpdklab
2024-01-09 21:16 dpdklab
2024-01-09 21:15 dpdklab
2024-01-09 21:13 dpdklab
2024-01-09 21:12 dpdklab
2024-01-09 21:11 dpdklab
2024-01-09 21:10 dpdklab
2024-01-09 21:09 dpdklab
2024-01-09 21:09 dpdklab
2024-01-09 21:07 dpdklab
2024-01-09 21:06 dpdklab
2024-01-09 21:05 dpdklab
2024-01-09 21:05 dpdklab
2024-01-09 21:04 dpdklab
2024-01-09 21:03 dpdklab
2024-01-09 21:03 dpdklab
2024-01-09 21:03 dpdklab
2024-01-09 21:02 dpdklab
2024-01-09 21:02 dpdklab
2024-01-09 21:02 dpdklab
2024-01-09 21:02 dpdklab
2024-01-09 21:01 dpdklab
2024-01-09 21:01 dpdklab
2024-01-09 21:01 dpdklab
2024-01-09 21:00 dpdklab
2024-01-09 20:59 dpdklab
2024-01-09 20:59 dpdklab
2024-01-09 20:59 dpdklab
2024-01-09 20:58 dpdklab
2024-01-09 20:58 dpdklab
2024-01-09 20:58 dpdklab
2024-01-09 20:58 dpdklab
2024-01-09 20:58 dpdklab
2024-01-09 20:57 dpdklab
2024-01-09 20:57 dpdklab
2024-01-09 20:57 dpdklab
2024-01-09 20:57 dpdklab
2024-01-09 20:56 dpdklab
2024-01-09 20:56 dpdklab
2024-01-09 20:56 dpdklab
2024-01-09 20:55 dpdklab
2024-01-09 20:55 dpdklab
2024-01-09 20:55 dpdklab
2024-01-09 20:55 dpdklab
2024-01-09 20:54 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=65a94a27.050a0220.f4a58.1df5SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=gakhil@marvell.com \
    --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).