From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| [GIT MASTER] fbba6db3640f9f623c29c452e1a6b057073e81d2
Date: Fri, 14 Jun 2024 01:44:37 -0700 (PDT) [thread overview]
Message-ID: <666c02f5.170a0220.f8163.7417SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net
fbba6db3640f9f623c29c452e1a6b057073e81d2 --> testing pass
Test environment and result as below:
+--------------------+----------------------+----------------------+
| Environment | compressdev_zlib_pmd | dpdk_fips_validation |
+====================+======================+======================+
| Ubuntu 22.04 (ARM) | PASS | SKIPPED |
+--------------------+----------------------+----------------------+
| Ubuntu 22.04 | PASS | SKIPPED |
+--------------------+----------------------+----------------------+
| Ubuntu 20.04 | SKIPPED | PASS |
+--------------------+----------------------+----------------------+
Ubuntu 22.04 (ARM)
Kernel: 5.15.0-97-generic
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Ubuntu 22.04
Kernel: 5.15.0-100-generic
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Ubuntu 20.04
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/29436/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-06-14 8:44 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 8:44 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-14 10:41 dpdklab
2024-06-14 10:27 dpdklab
2024-06-14 10:24 dpdklab
2024-06-14 10:20 dpdklab
2024-06-14 10:14 dpdklab
2024-06-14 10:12 dpdklab
2024-06-14 10:11 dpdklab
2024-06-14 10:11 dpdklab
2024-06-14 10:10 dpdklab
2024-06-14 10:10 dpdklab
2024-06-14 10:10 dpdklab
2024-06-14 10:07 dpdklab
2024-06-14 10:07 dpdklab
2024-06-14 10:03 dpdklab
2024-06-14 9:46 dpdklab
2024-06-14 9:31 dpdklab
2024-06-14 9:02 dpdklab
2024-06-14 8:48 dpdklab
2024-06-14 8:45 dpdklab
2024-06-14 8:43 dpdklab
2024-06-14 8:42 dpdklab
2024-06-14 8:41 dpdklab
2024-06-14 8:40 dpdklab
2024-06-14 8:40 dpdklab
2024-06-14 8:26 dpdklab
2024-06-14 8:18 dpdklab
2024-06-14 8:01 dpdklab
2024-06-14 8:00 dpdklab
2024-06-14 7:58 dpdklab
2024-06-14 7:58 dpdklab
2024-06-14 7:57 dpdklab
2024-06-14 7:50 dpdklab
2024-06-14 7:43 dpdklab
2024-06-14 7:43 dpdklab
2024-06-14 7:43 dpdklab
2024-06-14 7:42 dpdklab
2024-06-14 7:42 dpdklab
2024-06-14 7:41 dpdklab
2024-06-14 7:40 dpdklab
2024-06-14 7:39 dpdklab
2024-06-14 7:38 dpdklab
2024-06-14 7:37 dpdklab
2024-06-14 7:35 dpdklab
2024-06-14 7:34 dpdklab
2024-06-14 7:34 dpdklab
2024-06-14 7:33 dpdklab
2024-06-14 7:32 dpdklab
2024-06-14 7:32 dpdklab
2024-06-14 7:31 dpdklab
2024-06-14 7:30 dpdklab
2024-06-14 7:30 dpdklab
2024-06-14 7:30 dpdklab
2024-06-14 7:30 dpdklab
2024-06-14 7:30 dpdklab
2024-06-14 7:29 dpdklab
2024-06-14 7:28 dpdklab
2024-06-14 7:24 dpdklab
2024-06-14 7:23 dpdklab
2024-06-14 7:23 dpdklab
2024-06-14 7:22 dpdklab
2024-06-14 7:22 dpdklab
2024-06-14 7:20 dpdklab
2024-06-14 7:18 dpdklab
2024-06-14 7:17 dpdklab
2024-06-14 7:16 dpdklab
2024-06-14 7:16 dpdklab
2024-06-14 7:16 dpdklab
2024-06-14 7:15 dpdklab
2024-06-14 7:15 dpdklab
2024-06-14 7:15 dpdklab
2024-06-14 7:14 dpdklab
2024-06-14 7:03 dpdklab
2024-06-14 7:03 dpdklab
2024-06-14 7:03 dpdklab
2024-06-14 7:03 dpdklab
2024-06-14 7:02 dpdklab
2024-06-14 7:02 dpdklab
2024-06-14 7:02 dpdklab
2024-06-14 7:02 dpdklab
2024-06-14 7:01 dpdklab
2024-06-14 7:01 dpdklab
2024-06-14 7:01 dpdklab
2024-06-14 7:01 dpdklab
2024-06-14 7:00 dpdklab
2024-06-14 7:00 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=666c02f5.170a0220.f8163.7417SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dpdk-test-reports@iol.unh.edu \
--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).