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] 90790a65d2561d739b321b2722fa1a2a916af09c
Date: Fri, 09 Jun 2023 15:34:31 -0700 (PDT) [thread overview]
Message-ID: <6483a8f7.250a0220.6ad05.e489SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-crypto
90790a65d2561d739b321b2722fa1a2a916af09c --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/24819/
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-09 22:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 22:34 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-09 22:35 dpdklab
2023-06-09 22:35 dpdklab
2023-06-09 22:26 dpdklab
2023-06-08 22:11 dpdklab
2023-06-01 19:48 dpdklab
2023-06-01 19:39 dpdklab
2023-06-01 19:33 dpdklab
2023-06-01 19:28 dpdklab
2023-06-01 19:13 dpdklab
2023-06-01 17:39 dpdklab
2023-06-01 17:18 dpdklab
2023-06-01 16:29 dpdklab
2023-06-01 16:16 dpdklab
2023-06-01 16:15 dpdklab
2023-06-01 16:07 dpdklab
2023-06-01 16:06 dpdklab
2023-06-01 16:03 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=6483a8f7.250a0220.6ad05.e489SMTPIN_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).