From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 6484c847d4e48386904841d6b7062007f837dfb4
Date: Thu, 13 Jun 2024 18:50:36 -0700 (PDT) [thread overview]
Message-ID: <666ba1ec.050a0220.2412c.75c6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk
6484c847d4e48386904841d6b7062007f837dfb4 --> 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/29432/
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 1:50 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 1:50 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-14 5:52 dpdklab
2024-06-14 5:33 dpdklab
2024-06-14 4:55 dpdklab
2024-06-14 4:54 dpdklab
2024-06-14 4:38 dpdklab
2024-06-14 4:35 dpdklab
2024-06-14 4:34 dpdklab
2024-06-14 4:21 dpdklab
2024-06-14 4:11 dpdklab
2024-06-14 4:10 dpdklab
2024-06-14 4:01 dpdklab
2024-06-14 3:53 dpdklab
2024-06-14 3:53 dpdklab
2024-06-14 3:46 dpdklab
2024-06-14 3:31 dpdklab
2024-06-14 3:20 dpdklab
2024-06-14 3:20 dpdklab
2024-06-14 3:17 dpdklab
2024-06-14 3:17 dpdklab
2024-06-14 3:12 dpdklab
2024-06-14 3:09 dpdklab
2024-06-14 3:07 dpdklab
2024-06-14 3:06 dpdklab
2024-06-14 3:03 dpdklab
2024-06-14 3:02 dpdklab
2024-06-14 2:59 dpdklab
2024-06-14 2:58 dpdklab
2024-06-14 2:58 dpdklab
2024-06-14 2:58 dpdklab
2024-06-14 2:58 dpdklab
2024-06-14 2:57 dpdklab
2024-06-14 2:57 dpdklab
2024-06-14 2:57 dpdklab
2024-06-14 2:54 dpdklab
2024-06-14 2:52 dpdklab
2024-06-14 2:52 dpdklab
2024-06-14 2:51 dpdklab
2024-06-14 2:51 dpdklab
2024-06-14 2:51 dpdklab
2024-06-14 2:50 dpdklab
2024-06-14 2:50 dpdklab
2024-06-14 2:50 dpdklab
2024-06-14 2:49 dpdklab
2024-06-14 2:49 dpdklab
2024-06-14 2:48 dpdklab
2024-06-14 2:45 dpdklab
2024-06-14 2:43 dpdklab
2024-06-14 2:42 dpdklab
2024-06-14 2:41 dpdklab
2024-06-14 2:40 dpdklab
2024-06-14 2:39 dpdklab
2024-06-14 2:39 dpdklab
2024-06-14 2:38 dpdklab
2024-06-14 2:38 dpdklab
2024-06-14 2:37 dpdklab
2024-06-14 2:37 dpdklab
2024-06-14 2:37 dpdklab
2024-06-14 2:37 dpdklab
2024-06-14 2:36 dpdklab
2024-06-14 2:36 dpdklab
2024-06-14 2:36 dpdklab
2024-06-14 2:35 dpdklab
2024-06-14 2:34 dpdklab
2024-06-14 2:34 dpdklab
2024-06-14 2:34 dpdklab
2024-06-14 2:25 dpdklab
2024-06-14 2:24 dpdklab
2024-06-14 2:23 dpdklab
2024-06-14 2:23 dpdklab
2024-06-14 2:23 dpdklab
2024-06-14 2:23 dpdklab
2024-06-14 2:23 dpdklab
2024-06-14 2:22 dpdklab
2024-06-14 2:22 dpdklab
2024-06-14 2:22 dpdklab
2024-06-14 2:18 dpdklab
2024-06-14 2:11 dpdklab
2024-06-14 2:10 dpdklab
2024-06-14 2:10 dpdklab
2024-06-14 1:33 dpdklab
2024-06-14 1:32 dpdklab
2024-06-14 1:32 dpdklab
2024-06-14 1:31 dpdklab
2024-06-14 1:25 dpdklab
2024-06-14 1:25 dpdklab
2024-06-14 1:25 dpdklab
2024-06-14 1:13 dpdklab
2024-06-14 1:11 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=666ba1ec.050a0220.2412c.75c6SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--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).