From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Chenbo Xia <chenbox@nvidia.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: |SUCCESS| [GIT MASTER] d4cc6d4525f35078153f75ece05b7420aa11c37d
Date: Wed, 26 Jun 2024 02:49:59 -0700 (PDT) [thread overview]
Message-ID: <667be447.170a0220.9d94e.522eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-virtio
d4cc6d4525f35078153f75ece05b7420aa11c37d --> testing pass
Test environment and result as below:
+--------------------+----------------------+
| Environment | compressdev_zlib_pmd |
+====================+======================+
| Ubuntu 22.04 (ARM) | PASS |
+--------------------+----------------------+
| Ubuntu 22.04 | 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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/29590/
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-26 9:52 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 9:49 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-26 19:07 dpdklab
2024-06-26 18:43 dpdklab
2024-06-26 18:06 dpdklab
2024-06-26 14:18 dpdklab
2024-06-26 12:47 dpdklab
2024-06-26 12:00 dpdklab
2024-06-26 11:58 dpdklab
2024-06-26 11:55 dpdklab
2024-06-26 11:53 dpdklab
2024-06-26 11:48 dpdklab
2024-06-26 11:43 dpdklab
2024-06-26 11:41 dpdklab
2024-06-26 11:41 dpdklab
2024-06-26 11:40 dpdklab
2024-06-26 11:40 dpdklab
2024-06-26 11:40 dpdklab
2024-06-26 11:39 dpdklab
2024-06-26 11:39 dpdklab
2024-06-26 11:38 dpdklab
2024-06-26 11:37 dpdklab
2024-06-26 11:30 dpdklab
2024-06-26 11:28 dpdklab
2024-06-26 11:27 dpdklab
2024-06-26 11:27 dpdklab
2024-06-26 11:26 dpdklab
2024-06-26 11:26 dpdklab
2024-06-26 11:25 dpdklab
2024-06-26 11:24 dpdklab
2024-06-26 11:24 dpdklab
2024-06-26 11:23 dpdklab
2024-06-26 11:23 dpdklab
2024-06-26 11:23 dpdklab
2024-06-26 11:23 dpdklab
2024-06-26 11:22 dpdklab
2024-06-26 11:22 dpdklab
2024-06-26 11:22 dpdklab
2024-06-26 11:22 dpdklab
2024-06-26 11:21 dpdklab
2024-06-26 11:21 dpdklab
2024-06-26 11:21 dpdklab
2024-06-26 11:20 dpdklab
2024-06-26 11:19 dpdklab
2024-06-26 11:19 dpdklab
2024-06-26 11:19 dpdklab
2024-06-26 11:18 dpdklab
2024-06-26 11:18 dpdklab
2024-06-26 11:18 dpdklab
2024-06-26 11:17 dpdklab
2024-06-26 11:17 dpdklab
2024-06-26 11:16 dpdklab
2024-06-26 11:16 dpdklab
2024-06-26 11:15 dpdklab
2024-06-26 11:15 dpdklab
2024-06-26 11:15 dpdklab
2024-06-26 11:14 dpdklab
2024-06-26 11:13 dpdklab
2024-06-26 11:12 dpdklab
2024-06-26 11:11 dpdklab
2024-06-26 11:09 dpdklab
2024-06-26 11:08 dpdklab
2024-06-26 11:07 dpdklab
2024-06-26 11:07 dpdklab
2024-06-26 11:06 dpdklab
2024-06-26 11:05 dpdklab
2024-06-26 11:05 dpdklab
2024-06-26 10:48 dpdklab
2024-06-26 10:48 dpdklab
2024-06-26 10:47 dpdklab
2024-06-26 10:46 dpdklab
2024-06-26 10:46 dpdklab
2024-06-26 10:45 dpdklab
2024-06-26 10:45 dpdklab
2024-06-26 10:44 dpdklab
2024-06-26 10:43 dpdklab
2024-06-26 10:06 dpdklab
2024-06-26 9:52 dpdklab
2024-06-26 9:50 dpdklab
2024-06-26 9:49 dpdklab
2024-06-26 9:49 dpdklab
2024-06-26 9:48 dpdklab
2024-06-26 9:45 dpdklab
2024-06-26 9:42 dpdklab
2024-06-26 9:38 dpdklab
2024-06-26 9:32 dpdklab
2024-06-26 9:29 dpdklab
2024-06-26 9:28 dpdklab
2024-06-26 9:28 dpdklab
2024-06-26 9:20 dpdklab
2024-06-26 9:20 dpdklab
2024-06-26 7:14 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=667be447.170a0220.9d94e.522eSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=chenbox@nvidia.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=maxime.coquelin@redhat.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).