From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| [GIT MASTER] 523fd7b3adfdf5a87651e8ca33bc69223b3211d5
Date: Fri, 06 Sep 2024 07:29:12 -0700 (PDT) [thread overview]
Message-ID: <66db11b8.630a0220.f4ea5.7c14SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net
523fd7b3adfdf5a87651e8ca33bc69223b3211d5 --> testing pass
Upstream job id: Template-DTS-Pipeline#178885
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/30484/
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-06 14:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 14:29 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-17 12:07 dpdklab
2024-09-17 11:46 dpdklab
2024-09-07 23:08 dpdklab
2024-09-07 4:10 dpdklab
2024-09-07 2:27 dpdklab
2024-09-06 23:22 dpdklab
2024-09-06 21:33 dpdklab
2024-09-06 21:32 dpdklab
2024-09-06 19:03 dpdklab
2024-09-06 18:39 dpdklab
2024-09-06 17:23 dpdklab
2024-09-06 15:35 dpdklab
2024-09-06 11:36 dpdklab
2024-09-06 11:27 dpdklab
2024-09-06 11:25 dpdklab
2024-09-06 11:21 dpdklab
2024-09-06 11:19 dpdklab
2024-09-06 11:18 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=66db11b8.630a0220.f4ea5.7c14SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ferruh.yigit@amd.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).