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] 55bc9233a2065b3003e90710e4d139159f7c3ebf
Date: Tue, 17 Oct 2023 08:47:17 -0700 (PDT) [thread overview]
Message-ID: <652eac85.170a0220.e1734.52f8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk-next-crypto
55bc9233a2065b3003e90710e4d139159f7c3ebf --> 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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/26513/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-17 15:47 UTC|newest]
Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 15:47 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-18 20:33 dpdklab
2023-10-18 19:53 dpdklab
2023-10-18 3:28 dpdklab
2023-10-18 3:09 dpdklab
2023-10-18 3:03 dpdklab
2023-10-17 22:49 dpdklab
2023-10-17 22:43 dpdklab
2023-10-17 22:20 dpdklab
2023-10-17 17:45 dpdklab
2023-10-17 17:11 dpdklab
2023-10-17 17:01 dpdklab
2023-10-17 16:31 dpdklab
2023-10-17 16:11 dpdklab
2023-10-17 16:10 dpdklab
2023-10-17 16:05 dpdklab
2023-10-17 16:05 dpdklab
2023-10-17 16:04 dpdklab
2023-10-17 16:02 dpdklab
2023-10-17 15:59 dpdklab
2023-10-17 15:58 dpdklab
2023-10-17 15:58 dpdklab
2023-10-17 15:56 dpdklab
2023-10-17 15:55 dpdklab
2023-10-17 15:55 dpdklab
2023-10-17 15:53 dpdklab
2023-10-17 15:53 dpdklab
2023-10-17 15:52 dpdklab
2023-10-17 15:52 dpdklab
2023-10-17 15:51 dpdklab
2023-10-17 15:51 dpdklab
2023-10-17 15:50 dpdklab
2023-10-17 15:50 dpdklab
2023-10-17 15:50 dpdklab
2023-10-17 15:50 dpdklab
2023-10-17 15:50 dpdklab
2023-10-17 15:49 dpdklab
2023-10-17 15:49 dpdklab
2023-10-17 15:49 dpdklab
2023-10-17 15:49 dpdklab
2023-10-17 15:49 dpdklab
2023-10-17 15:49 dpdklab
2023-10-17 15:49 dpdklab
2023-10-17 15:48 dpdklab
2023-10-17 15:48 dpdklab
2023-10-17 15:47 dpdklab
2023-10-17 15:47 dpdklab
2023-10-17 2:46 dpdklab
2023-10-17 2:41 dpdklab
2023-10-17 2:23 dpdklab
2023-10-17 1:34 dpdklab
2023-10-17 1:28 dpdklab
2023-10-17 1:27 dpdklab
2023-10-17 1:25 dpdklab
2023-10-17 1:25 dpdklab
2023-10-17 1:24 dpdklab
2023-10-17 1:23 dpdklab
2023-10-17 1:23 dpdklab
2023-10-17 1:20 dpdklab
2023-10-17 1:19 dpdklab
2023-10-17 1:18 dpdklab
2023-10-17 1:18 dpdklab
2023-10-17 1:17 dpdklab
2023-10-17 1:16 dpdklab
2023-10-17 1:15 dpdklab
2023-10-17 1:15 dpdklab
2023-10-17 1:15 dpdklab
2023-10-17 1:14 dpdklab
2023-10-17 1:14 dpdklab
2023-10-17 1:14 dpdklab
2023-10-17 1:14 dpdklab
2023-10-17 1:14 dpdklab
2023-10-17 1:14 dpdklab
2023-10-17 1:14 dpdklab
2023-10-17 1:14 dpdklab
2023-10-17 1:12 dpdklab
2023-10-17 1:12 dpdklab
2023-10-17 1:12 dpdklab
2023-10-17 1:11 dpdklab
2023-10-17 1:11 dpdklab
2023-10-17 1:11 dpdklab
2023-10-17 1:11 dpdklab
2023-10-17 1:11 dpdklab
2023-10-17 1:11 dpdklab
2023-10-17 1:11 dpdklab
2023-10-17 1:11 dpdklab
2023-10-17 1:11 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=652eac85.170a0220.e1734.52f8SMTPIN_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).