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] 077a7044cc5b2533410f691c8db6fb4f6667b1ca
Date: Sun, 08 Dec 2024 21:41:23 -0800 (PST) [thread overview]
Message-ID: <67568303.170a0220.2b4418.8bf7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: tags/v22.11
077a7044cc5b2533410f691c8db6fb4f6667b1ca --> testing pass
Upstream job id: Template-DTS-Pipeline#201666
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/31878/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-12-09 5:41 UTC|newest]
Thread overview: 97+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 5:41 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-09 7:46 dpdklab
2024-12-09 7:44 dpdklab
2024-12-09 7:38 dpdklab
2024-12-09 7:26 dpdklab
2024-12-09 7:16 dpdklab
2024-12-09 7:14 dpdklab
2024-12-09 7:09 dpdklab
2024-12-09 6:52 dpdklab
2024-12-09 6:31 dpdklab
2024-12-09 6:28 dpdklab
2024-12-09 6:22 dpdklab
2024-12-09 6:14 dpdklab
2024-12-08 9:35 dpdklab
2024-12-08 7:55 dpdklab
2024-12-08 7:29 dpdklab
2024-12-08 7:27 dpdklab
2024-12-08 7:07 dpdklab
2024-12-08 7:04 dpdklab
2024-12-08 7:01 dpdklab
2024-12-08 6:52 dpdklab
2024-12-08 6:48 dpdklab
2024-12-08 6:47 dpdklab
2024-12-08 6:38 dpdklab
2024-12-08 6:21 dpdklab
2024-12-08 6:15 dpdklab
2024-12-08 5:53 dpdklab
2024-12-07 9:36 dpdklab
2024-12-07 7:49 dpdklab
2024-12-07 7:08 dpdklab
2024-12-07 7:05 dpdklab
2024-12-07 6:47 dpdklab
2024-12-07 6:32 dpdklab
2024-12-07 6:19 dpdklab
2024-12-07 6:03 dpdklab
2024-12-07 6:03 dpdklab
2024-12-07 5:55 dpdklab
2024-12-07 5:55 dpdklab
2024-12-07 5:54 dpdklab
2024-12-07 5:53 dpdklab
2024-12-07 5:42 dpdklab
2024-12-07 5:41 dpdklab
2024-12-07 5:40 dpdklab
2024-12-07 5:35 dpdklab
2024-12-07 5:30 dpdklab
2024-12-07 5:30 dpdklab
2024-12-07 1:51 dpdklab
2024-12-07 1:14 dpdklab
2024-12-06 23:47 dpdklab
2024-12-06 23:40 dpdklab
2024-12-06 23:39 dpdklab
2024-12-06 23:37 dpdklab
2024-12-06 23:32 dpdklab
2024-12-06 23:27 dpdklab
2024-12-06 23:24 dpdklab
2024-12-06 23:20 dpdklab
2024-12-06 23:14 dpdklab
2024-12-06 8:55 dpdklab
2024-12-06 8:27 dpdklab
2024-12-06 7:49 dpdklab
2024-12-06 7:47 dpdklab
2024-12-06 6:54 dpdklab
2024-12-06 6:39 dpdklab
2024-12-06 6:33 dpdklab
2024-12-06 6:26 dpdklab
2024-12-06 6:06 dpdklab
2024-12-06 6:02 dpdklab
2024-12-06 6:02 dpdklab
2024-12-06 5:40 dpdklab
2024-12-05 8:51 dpdklab
2024-12-05 8:29 dpdklab
2024-12-05 8:09 dpdklab
2024-12-05 7:59 dpdklab
2024-12-05 7:56 dpdklab
2024-12-05 7:54 dpdklab
2024-12-05 7:52 dpdklab
2024-12-05 6:41 dpdklab
2024-12-05 6:28 dpdklab
2024-12-05 6:20 dpdklab
2024-12-05 6:14 dpdklab
2024-12-05 6:02 dpdklab
2024-12-05 6:02 dpdklab
2024-12-04 14:59 dpdklab
2024-12-04 14:33 dpdklab
2024-12-04 14:31 dpdklab
2024-12-04 14:17 dpdklab
2024-12-04 14:14 dpdklab
2024-12-04 14:04 dpdklab
2024-12-04 10:07 dpdklab
2024-12-04 9:01 dpdklab
2024-12-04 8:54 dpdklab
2024-12-04 8:36 dpdklab
2024-12-04 7:35 dpdklab
2024-12-04 6:46 dpdklab
2024-12-04 6:37 dpdklab
2024-12-04 6:30 dpdklab
2024-12-04 5:54 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=67568303.170a0220.2b4418.8bf7SMTPIN_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).