From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>
Subject: |SUCCESS| [GIT MASTER] 03f2ed63a5f4e4b57365e358b49095ef4a82cf7d
Date: Sat, 29 Mar 2025 21:21:07 -0700 (PDT) [thread overview]
Message-ID: <67e8c6b3.050a0220.387b99.afd0SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: tags/v24.11
03f2ed63a5f4e4b57365e358b49095ef4a82cf7d --> testing pass
Upstream job id: Template-DTS-Pipeline#219575
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/33098/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2025-03-30 4:21 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-30 4:21 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-03 6:32 dpdklab
2025-04-03 5:59 dpdklab
2025-04-03 5:50 dpdklab
2025-04-03 5:35 dpdklab
2025-04-03 5:31 dpdklab
2025-04-03 5:23 dpdklab
2025-04-03 5:05 dpdklab
2025-04-02 8:21 dpdklab
2025-04-02 7:20 dpdklab
2025-04-02 6:37 dpdklab
2025-04-02 6:15 dpdklab
2025-04-02 5:57 dpdklab
2025-04-02 5:18 dpdklab
2025-04-02 5:17 dpdklab
2025-04-02 4:45 dpdklab
2025-04-02 4:38 dpdklab
2025-04-02 4:36 dpdklab
2025-04-02 4:32 dpdklab
2025-04-02 4:29 dpdklab
2025-04-02 4:23 dpdklab
2025-04-02 4:17 dpdklab
2025-04-02 4:17 dpdklab
2025-04-01 7:41 dpdklab
2025-04-01 6:35 dpdklab
2025-04-01 6:32 dpdklab
2025-04-01 6:16 dpdklab
2025-04-01 6:12 dpdklab
2025-04-01 6:02 dpdklab
2025-04-01 5:34 dpdklab
2025-04-01 5:31 dpdklab
2025-04-01 5:31 dpdklab
2025-04-01 5:28 dpdklab
2025-04-01 5:17 dpdklab
2025-04-01 4:42 dpdklab
2025-04-01 4:36 dpdklab
2025-03-31 10:07 dpdklab
2025-03-31 7:30 dpdklab
2025-03-31 6:57 dpdklab
2025-03-31 6:10 dpdklab
2025-03-31 5:55 dpdklab
2025-03-31 5:42 dpdklab
2025-03-31 5:34 dpdklab
2025-03-31 5:33 dpdklab
2025-03-31 5:17 dpdklab
2025-03-31 5:16 dpdklab
2025-03-31 5:07 dpdklab
2025-03-31 5:06 dpdklab
2025-03-31 4:52 dpdklab
2025-03-31 4:44 dpdklab
2025-03-30 7:58 dpdklab
2025-03-30 7:30 dpdklab
2025-03-30 7:27 dpdklab
2025-03-30 6:56 dpdklab
2025-03-30 6:07 dpdklab
2025-03-30 5:59 dpdklab
2025-03-30 5:30 dpdklab
2025-03-30 4:52 dpdklab
2025-03-30 4:37 dpdklab
2025-03-30 4:36 dpdklab
2025-03-30 4:32 dpdklab
2025-03-30 4:28 dpdklab
2025-03-30 4:17 dpdklab
2025-03-30 4:17 dpdklab
2025-03-29 10:17 dpdklab
2025-03-29 8:06 dpdklab
2025-03-29 7:59 dpdklab
2025-03-29 7:43 dpdklab
2025-03-29 7:04 dpdklab
2025-03-29 6:35 dpdklab
2025-03-29 6:26 dpdklab
2025-03-29 6:14 dpdklab
2025-03-29 6:14 dpdklab
2025-03-29 5:50 dpdklab
2025-03-29 5:48 dpdklab
2025-03-29 5:35 dpdklab
2025-03-29 5:20 dpdklab
2025-03-29 5:19 dpdklab
2025-03-29 5:13 dpdklab
2025-03-29 5:13 dpdklab
2025-03-29 4:58 dpdklab
2025-03-29 4:49 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=67e8c6b3.050a0220.387b99.afd0SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ktraynor@redhat.com \
--cc=test-report@dpdk.org \
--cc=xuemingl@nvidia.com \
/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).