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] fa9d8629f800e85054b5c69678c3aeced4866e0f
Date: Thu, 21 Nov 2024 10:23:07 -0800 (PST) [thread overview]
Message-ID: <673f7a8b.050a0220.a4943.09a6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-eventdev
fa9d8629f800e85054b5c69678c3aeced4866e0f --> testing pass
Upstream job id: Template-DTS-Pipeline#198112
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/31673/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-11-21 18:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 18:23 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-21 23:43 dpdklab
2024-11-21 22:42 dpdklab
2024-11-21 22:16 dpdklab
2024-11-21 21:53 dpdklab
2024-11-21 21:36 dpdklab
2024-11-21 21:26 dpdklab
2024-11-21 21:15 dpdklab
2024-11-21 20:47 dpdklab
2024-11-21 20:37 dpdklab
2024-11-21 20:25 dpdklab
2024-11-21 20:02 dpdklab
2024-11-21 19:48 dpdklab
2024-11-21 19:34 dpdklab
2024-11-21 19:20 dpdklab
2024-11-21 19:12 dpdklab
2024-11-19 11:24 dpdklab
2024-11-18 18:51 dpdklab
2024-11-18 18:32 dpdklab
2024-11-18 18:31 dpdklab
2024-11-18 18:30 dpdklab
2024-11-18 18:29 dpdklab
2024-11-18 17:59 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=673f7a8b.050a0220.a4943.09a6SMTPIN_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).