From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| [GIT MASTER] 86e09318b9be354222de6407594caad182e21a8e
Date: Fri, 09 Feb 2024 02:26:03 -0800 (PST) [thread overview]
Message-ID: <65c5fdbb.0d0a0220.efd31.5e7fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net
86e09318b9be354222de6407594caad182e21a8e --> testing pass
Test environment and result as below:
+--------------+----------------------+----------------------+
| Environment | dpdk_fips_validation | compressdev_zlib_pmd |
+==============+======================+======================+
| Ubuntu 20.04 | PASS | SKIPPED |
+--------------+----------------------+----------------------+
| Ubuntu 22.04 | SKIPPED | PASS |
+--------------+----------------------+----------------------+
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
Ubuntu 22.04
Kernel: 5.15.0-91-generic
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/27952/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-09 10:26 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 10:26 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-09 10:54 dpdklab
2024-02-09 10:20 dpdklab
2024-02-09 9:58 dpdklab
2024-02-09 9:49 dpdklab
2024-02-09 8:53 dpdklab
2024-02-09 8:04 dpdklab
2024-02-09 7:53 dpdklab
2024-02-09 7:53 dpdklab
2024-02-09 7:52 dpdklab
2024-02-09 7:51 dpdklab
2024-02-09 7:49 dpdklab
2024-02-09 7:48 dpdklab
2024-02-09 7:48 dpdklab
2024-02-09 7:46 dpdklab
2024-02-09 7:46 dpdklab
2024-02-09 7:44 dpdklab
2024-02-09 7:42 dpdklab
2024-02-09 7:42 dpdklab
2024-02-09 7:41 dpdklab
2024-02-09 7:40 dpdklab
2024-02-09 7:40 dpdklab
2024-02-09 7:40 dpdklab
2024-02-09 7:39 dpdklab
2024-02-09 7:39 dpdklab
2024-02-09 7:39 dpdklab
2024-02-09 7:39 dpdklab
2024-02-09 7:39 dpdklab
2024-02-09 7:38 dpdklab
2024-02-09 7:38 dpdklab
2024-02-09 7:38 dpdklab
2024-02-09 7:38 dpdklab
2024-02-09 7:38 dpdklab
2024-02-09 7:38 dpdklab
2024-02-09 7:37 dpdklab
2024-02-09 7:37 dpdklab
2024-02-09 7:37 dpdklab
2024-02-09 7:37 dpdklab
2024-02-09 7:37 dpdklab
2024-02-09 7:36 dpdklab
2024-02-09 7:36 dpdklab
2024-02-09 7:36 dpdklab
2024-02-09 7:36 dpdklab
2024-02-09 7:36 dpdklab
2024-02-09 7:36 dpdklab
2024-02-09 7:35 dpdklab
2024-02-09 7:35 dpdklab
2024-02-09 7:35 dpdklab
2024-02-09 7:35 dpdklab
2024-02-09 7:34 dpdklab
2024-02-09 7:34 dpdklab
2024-02-09 7:33 dpdklab
2024-02-09 7:33 dpdklab
2024-02-09 7:33 dpdklab
2024-02-09 7:32 dpdklab
2024-02-09 7:31 dpdklab
2024-02-09 7:31 dpdklab
2024-02-09 7:30 dpdklab
2024-02-09 7:30 dpdklab
2024-02-09 7:28 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=65c5fdbb.0d0a0220.efd31.5e7fSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=ferruh.yigit@amd.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).