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] b7b8de26f34d39c8aaded44d8a468da5e68f19da
Date: Wed, 30 Aug 2023 12:39:55 -0700 (PDT) [thread overview]
Message-ID: <64ef9b0b.a70a0220.b8e62.f180SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk-next-crypto
b7b8de26f34d39c8aaded44d8a468da5e68f19da --> 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
Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-155-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/tarballs/25984/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-30 19:40 UTC|newest]
Thread overview: 133+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 19:39 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-31 13:29 dpdklab
2023-08-31 2:49 dpdklab
2023-08-31 2:44 dpdklab
2023-08-31 2:39 dpdklab
2023-08-31 2:23 dpdklab
2023-08-31 2:17 dpdklab
2023-08-31 2:12 dpdklab
2023-08-31 1:26 dpdklab
2023-08-31 1:20 dpdklab
2023-08-31 1:20 dpdklab
2023-08-31 1:18 dpdklab
2023-08-31 1:18 dpdklab
2023-08-31 1:15 dpdklab
2023-08-31 1:15 dpdklab
2023-08-31 1:14 dpdklab
2023-08-31 1:12 dpdklab
2023-08-31 1:12 dpdklab
2023-08-31 1:12 dpdklab
2023-08-31 1:10 dpdklab
2023-08-31 1:08 dpdklab
2023-08-31 1:06 dpdklab
2023-08-31 1:06 dpdklab
2023-08-31 1:06 dpdklab
2023-08-31 1:06 dpdklab
2023-08-31 1:05 dpdklab
2023-08-31 1:05 dpdklab
2023-08-31 1:05 dpdklab
2023-08-31 1:05 dpdklab
2023-08-31 1:05 dpdklab
2023-08-31 1:05 dpdklab
2023-08-31 1:05 dpdklab
2023-08-31 1:05 dpdklab
2023-08-31 1:05 dpdklab
2023-08-31 1:05 dpdklab
2023-08-31 1:05 dpdklab
2023-08-31 1:05 dpdklab
2023-08-31 1:05 dpdklab
2023-08-31 1:05 dpdklab
2023-08-31 1:05 dpdklab
2023-08-31 1:04 dpdklab
2023-08-31 1:04 dpdklab
2023-08-31 1:02 dpdklab
2023-08-31 1:00 dpdklab
2023-08-31 0:59 dpdklab
2023-08-30 19:21 dpdklab
2023-08-30 18:31 dpdklab
2023-08-30 18:21 dpdklab
2023-08-30 18:02 dpdklab
2023-08-30 17:49 dpdklab
2023-08-30 17:42 dpdklab
2023-08-30 17:32 dpdklab
2023-08-30 17:05 dpdklab
2023-08-30 16:14 dpdklab
2023-08-30 16:08 dpdklab
2023-08-30 16:08 dpdklab
2023-08-30 16:04 dpdklab
2023-08-30 16:03 dpdklab
2023-08-30 16:02 dpdklab
2023-08-30 16:01 dpdklab
2023-08-30 16:01 dpdklab
2023-08-30 15:59 dpdklab
2023-08-30 15:57 dpdklab
2023-08-30 15:56 dpdklab
2023-08-30 15:54 dpdklab
2023-08-30 15:53 dpdklab
2023-08-30 15:52 dpdklab
2023-08-30 15:51 dpdklab
2023-08-30 15:51 dpdklab
2023-08-30 15:50 dpdklab
2023-08-30 15:50 dpdklab
2023-08-30 15:50 dpdklab
2023-08-30 15:50 dpdklab
2023-08-30 15:49 dpdklab
2023-08-30 15:49 dpdklab
2023-08-30 15:49 dpdklab
2023-08-30 15:49 dpdklab
2023-08-30 15:49 dpdklab
2023-08-30 15:48 dpdklab
2023-08-30 15:48 dpdklab
2023-08-30 15:48 dpdklab
2023-08-30 15:48 dpdklab
2023-08-30 15:48 dpdklab
2023-08-30 15:47 dpdklab
2023-08-30 15:47 dpdklab
2023-08-30 15:47 dpdklab
2023-08-30 15:47 dpdklab
2023-08-30 15:46 dpdklab
2023-08-30 15:46 dpdklab
2023-08-30 15:45 dpdklab
2023-08-30 15:45 dpdklab
2023-08-30 6:15 dpdklab
2023-08-30 5:50 dpdklab
2023-08-30 5:31 dpdklab
2023-08-30 5:02 dpdklab
2023-08-30 5:01 dpdklab
2023-08-30 3:15 dpdklab
2023-08-30 2:17 dpdklab
2023-08-30 1:26 dpdklab
2023-08-30 1:24 dpdklab
2023-08-30 1:24 dpdklab
2023-08-30 1:21 dpdklab
2023-08-30 1:20 dpdklab
2023-08-30 1:18 dpdklab
2023-08-30 1:16 dpdklab
2023-08-30 1:15 dpdklab
2023-08-30 1:14 dpdklab
2023-08-30 1:10 dpdklab
2023-08-30 1:09 dpdklab
2023-08-30 1:08 dpdklab
2023-08-30 1:07 dpdklab
2023-08-30 1:06 dpdklab
2023-08-30 1:04 dpdklab
2023-08-30 1:04 dpdklab
2023-08-30 1:04 dpdklab
2023-08-30 1:04 dpdklab
2023-08-30 1:04 dpdklab
2023-08-30 1:04 dpdklab
2023-08-30 1:04 dpdklab
2023-08-30 1:04 dpdklab
2023-08-30 1:04 dpdklab
2023-08-30 1:04 dpdklab
2023-08-30 1:04 dpdklab
2023-08-30 1:03 dpdklab
2023-08-30 1:03 dpdklab
2023-08-30 1:03 dpdklab
2023-08-30 1:03 dpdklab
2023-08-30 1:03 dpdklab
2023-08-30 1:03 dpdklab
2023-08-30 1:03 dpdklab
2023-08-30 1:02 dpdklab
2023-08-30 1:01 dpdklab
2023-08-30 0:59 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=64ef9b0b.a70a0220.b8e62.f180SMTPIN_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).