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] 050de60d8a5cef8b7c10b4471905ca8bf69d670e
Date: Tue, 13 Jun 2023 09:25:02 -0700 (PDT) [thread overview]
Message-ID: <6488985e.6b0a0220.dec8c.214aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk-next-crypto
050de60d8a5cef8b7c10b4471905ca8bf69d670e --> functional testing pass
Test environment and result as below:
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
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/tarballs/24991/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-06-13 16:25 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 16:25 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-16 17:54 dpdklab
2023-06-15 19:51 dpdklab
2023-06-15 19:41 dpdklab
2023-06-15 19:36 dpdklab
2023-06-15 19:32 dpdklab
2023-06-15 19:16 dpdklab
2023-06-15 13:35 dpdklab
2023-06-15 13:34 dpdklab
2023-06-15 8:52 dpdklab
2023-06-15 6:47 dpdklab
2023-06-15 3:13 dpdklab
2023-06-15 3:12 dpdklab
2023-06-15 3:00 dpdklab
2023-06-15 2:58 dpdklab
2023-06-15 2:50 dpdklab
2023-06-15 2:45 dpdklab
2023-06-15 2:42 dpdklab
2023-06-15 2:36 dpdklab
2023-06-15 2:35 dpdklab
2023-06-15 2:26 dpdklab
2023-06-15 2:26 dpdklab
2023-06-15 2:23 dpdklab
2023-06-15 2:20 dpdklab
2023-06-15 2:17 dpdklab
2023-06-15 1:29 dpdklab
2023-06-15 1:17 dpdklab
2023-06-15 1:15 dpdklab
2023-06-15 1:14 dpdklab
2023-06-15 1:14 dpdklab
2023-06-15 1:12 dpdklab
2023-06-14 20:37 dpdklab
2023-06-14 8:13 dpdklab
2023-06-14 8:09 dpdklab
2023-06-14 8:05 dpdklab
2023-06-14 6:30 dpdklab
2023-06-14 2:42 dpdklab
2023-06-14 2:36 dpdklab
2023-06-14 2:36 dpdklab
2023-06-14 2:32 dpdklab
2023-06-14 2:27 dpdklab
2023-06-14 2:23 dpdklab
2023-06-14 2:07 dpdklab
2023-06-13 21:53 dpdklab
2023-06-13 21:52 dpdklab
2023-06-13 20:08 dpdklab
2023-06-13 17:58 dpdklab
2023-06-13 17:40 dpdklab
2023-06-13 17:34 dpdklab
2023-06-13 16:28 dpdklab
2023-06-13 16:26 dpdklab
2023-06-13 16:26 dpdklab
2023-06-13 16:24 dpdklab
2023-06-13 16:15 dpdklab
2023-06-13 14:54 dpdklab
2023-06-13 12:41 dpdklab
2023-06-13 12:39 dpdklab
2023-06-13 11:54 dpdklab
2023-06-13 11:34 dpdklab
2023-06-13 11:34 dpdklab
2023-06-13 11:30 dpdklab
2023-06-13 11:30 dpdklab
2023-06-13 11:24 dpdklab
2023-06-13 8:10 dpdklab
2023-06-13 7:37 dpdklab
2023-06-13 7:34 dpdklab
2023-06-13 7:01 dpdklab
2023-06-13 6:22 dpdklab
2023-06-13 6:10 dpdklab
2023-06-13 4:26 dpdklab
2023-06-13 3:40 dpdklab
2023-06-13 3:33 dpdklab
2023-06-13 3:20 dpdklab
2023-06-13 3:13 dpdklab
2023-06-13 3:13 dpdklab
2023-06-13 3:04 dpdklab
2023-06-13 2:59 dpdklab
2023-06-13 2:59 dpdklab
2023-06-13 2:48 dpdklab
2023-06-13 2:39 dpdklab
2023-06-13 2:36 dpdklab
2023-06-13 2:35 dpdklab
2023-06-13 2:28 dpdklab
2023-06-13 2:23 dpdklab
2023-06-13 2:16 dpdklab
2023-06-13 2:12 dpdklab
2023-06-13 1:25 dpdklab
2023-06-13 1:10 dpdklab
2023-06-13 1:07 dpdklab
2023-06-13 1:07 dpdklab
2023-06-13 1:02 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=6488985e.6b0a0220.dec8c.214aSMTPIN_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).