From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Jerin Jacob <jerinj@marvell.com>
Subject: |SUCCESS| [GIT MASTER] b5293ef3ab72febc2fc8fe444347a232b9f005d5
Date: Wed, 18 Sep 2024 12:05:02 -0700 (PDT) [thread overview]
Message-ID: <66eb245e.050a0220.12295f.5941SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-eventdev
b5293ef3ab72febc2fc8fe444347a232b9f005d5 --> testing pass
Upstream job id: Template-DTS-Pipeline#182118
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/30648/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-09-18 19:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 19:05 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-22 16:53 dpdklab
2024-09-22 16:42 dpdklab
2024-09-19 19:45 dpdklab
2024-09-19 2:07 dpdklab
2024-09-19 0:01 dpdklab
2024-09-18 22:54 dpdklab
2024-09-18 22:53 dpdklab
2024-09-18 22:08 dpdklab
2024-09-18 21:54 dpdklab
2024-09-18 20:06 dpdklab
2024-09-18 20:06 dpdklab
2024-09-18 20:05 dpdklab
2024-09-18 19:53 dpdklab
2024-09-18 19:49 dpdklab
2024-09-18 19:40 dpdklab
2024-09-18 19:38 dpdklab
2024-09-18 19:19 dpdklab
2024-09-18 18:18 dpdklab
2024-09-18 18:05 dpdklab
2024-09-18 17:55 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=66eb245e.050a0220.12295f.5941SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=jerinj@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).