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] 3317515e9377c13e458e31a64f8987a9d1f2eaf6
Date: Thu, 18 Jul 2024 01:29:21 -0700 (PDT) [thread overview]
Message-ID: <6698d261.b00a0220.285f3c.1482SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net
3317515e9377c13e458e31a64f8987a9d1f2eaf6 --> testing pass
Upstream job id: Template-DTS-Pipeline#168800
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/29898/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-07-18 8:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 8:29 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-18 21:00 dpdklab
2024-07-18 13:40 dpdklab
2024-07-18 12:50 dpdklab
2024-07-18 12:30 dpdklab
2024-07-18 12:26 dpdklab
2024-07-18 12:24 dpdklab
2024-07-18 12:21 dpdklab
2024-07-18 12:17 dpdklab
2024-07-18 11:40 dpdklab
2024-07-18 9:47 dpdklab
2024-07-18 9:22 dpdklab
2024-07-18 9:01 dpdklab
2024-07-18 8:38 dpdklab
2024-07-18 8:26 dpdklab
2024-07-18 8:26 dpdklab
2024-07-18 8:26 dpdklab
2024-07-18 8:21 dpdklab
2024-07-18 8:15 dpdklab
2024-07-18 8:12 dpdklab
2024-07-18 8:07 dpdklab
2024-07-18 8:06 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=6698d261.b00a0220.285f3c.1482SMTPIN_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).