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] 95ff85f8acb0c7c912fd29b01428377fcbf1112a
Date: Wed, 26 Feb 2025 11:21:59 -0800 (PST) [thread overview]
Message-ID: <67bf69d7.050a0220.1484d5.e9aeSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-crypto
95ff85f8acb0c7c912fd29b01428377fcbf1112a --> testing pass
Upstream job id: Template-DTS-Pipeline#214720
Test environment and result as below:
+--------------------+----------------------+
| Environment | compressdev_zlib_pmd |
+====================+======================+
| Ubuntu 22.04 (ARM) | PASS |
+--------------------+----------------------+
Ubuntu 22.04 (ARM)
Kernel: 5.15.0-97-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/32728/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2025-02-26 19:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 19:21 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-26 21:58 dpdklab
2025-02-26 20:56 dpdklab
2025-02-26 20:25 dpdklab
2025-02-26 20:20 dpdklab
2025-02-26 20:10 dpdklab
2025-02-26 19:50 dpdklab
2025-02-26 19:38 dpdklab
2025-02-26 19:06 dpdklab
2025-02-26 11:04 dpdklab
2025-02-26 8:02 dpdklab
2025-02-26 8:01 dpdklab
2025-02-26 7:00 dpdklab
2025-02-26 6:11 dpdklab
2025-02-26 5:22 dpdklab
2025-02-26 4:47 dpdklab
2025-02-26 2:02 dpdklab
2025-02-18 3:59 dpdklab
2025-02-18 3:47 dpdklab
2025-02-12 7:18 dpdklab
2025-02-12 2:39 dpdklab
2025-02-11 21:33 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=67bf69d7.050a0220.1484d5.e9aeSMTPIN_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).