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] 1e6cb8f290b65d27c94e0caf108d6c35c30fe42b
Date: Mon, 16 Oct 2023 10:45:13 -0700 (PDT) [thread overview]
Message-ID: <652d76a9.050a0220.95f0b.7534SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-crypto
1e6cb8f290b65d27c94e0caf108d6c35c30fe42b --> testing pass
Test environment and result as below:
+------------------+----------------+
| Environment | dpdk_unit_test |
+==================+================+
| Debian Bullseye | PASS |
+------------------+----------------+
| CentOS Stream 8 | PASS |
+------------------+----------------+
| Debian Buster | PASS |
+------------------+----------------+
| CentOS Stream 9 | PASS |
+------------------+----------------+
| Fedora 38 | PASS |
+------------------+----------------+
| Ubuntu 20.04 | PASS |
+------------------+----------------+
| Fedora 37 | PASS |
+------------------+----------------+
| openSUSE Leap 15 | PASS |
+------------------+----------------+
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/26496/
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-16 17:45 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 17:45 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-16 18:52 dpdklab
2023-10-16 18:43 dpdklab
2023-10-16 18:38 dpdklab
2023-10-16 18:36 dpdklab
2023-10-16 18:30 dpdklab
2023-10-16 18:29 dpdklab
2023-10-16 17:57 dpdklab
2023-10-16 17:48 dpdklab
2023-10-16 17:47 dpdklab
2023-10-16 17:45 dpdklab
2023-10-16 17:45 dpdklab
2023-10-16 17:45 dpdklab
2023-10-16 17:45 dpdklab
2023-10-16 17:43 dpdklab
2023-10-16 17:43 dpdklab
2023-10-16 17:43 dpdklab
2023-10-16 17:43 dpdklab
2023-10-16 17:43 dpdklab
2023-10-16 17:43 dpdklab
2023-10-16 17:43 dpdklab
2023-10-16 17:42 dpdklab
2023-10-16 17:42 dpdklab
2023-10-16 17:42 dpdklab
2023-10-16 17:42 dpdklab
2023-10-16 17:41 dpdklab
2023-10-16 17:41 dpdklab
2023-10-16 17:40 dpdklab
2023-10-16 17:39 dpdklab
2023-10-16 17:39 dpdklab
2023-10-16 17:38 dpdklab
2023-10-16 17:38 dpdklab
2023-10-16 17:38 dpdklab
2023-10-16 17:38 dpdklab
2023-10-16 17:38 dpdklab
2023-10-16 17:37 dpdklab
2023-10-16 17:37 dpdklab
2023-10-16 17:37 dpdklab
2023-10-16 17:37 dpdklab
2023-10-16 17:36 dpdklab
2023-10-16 17:33 dpdklab
2023-10-16 17:28 dpdklab
2023-10-16 17:14 dpdklab
2023-10-16 17:09 dpdklab
2023-10-16 16:54 dpdklab
2023-10-16 16:34 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=652d76a9.050a0220.95f0b.7534SMTPIN_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).