automatic DPDK test reports
 help / color / mirror / Atom feed
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] 5cce3d463a99dbb5e7797faaed6c68df6c2b549a
Date: Tue, 03 Sep 2024 01:11:22 -0700 (PDT)	[thread overview]
Message-ID: <66d6c4aa.050a0220.ce24f.0586SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk-next-net

5cce3d463a99dbb5e7797faaed6c68df6c2b549a --> testing pass

Upstream job id: Template-DTS-Pipeline#178102

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/30428/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2024-09-03  8:11 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-03  8:11 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-18 17:22 dpdklab
2024-09-18 16:20 dpdklab
2024-09-03 12:38 dpdklab
2024-09-03 12:02 dpdklab
2024-09-03 12:00 dpdklab
2024-09-03 11:59 dpdklab
2024-09-03 11:02 dpdklab
2024-09-03 11:01 dpdklab
2024-09-03 10:59 dpdklab
2024-09-03 10:59 dpdklab
2024-09-03 10:50 dpdklab
2024-09-03 10:30 dpdklab
2024-09-03  9:53 dpdklab
2024-09-03  9:44 dpdklab
2024-09-03  9:44 dpdklab
2024-09-03  9:36 dpdklab
2024-09-03  8:51 dpdklab
2024-09-03  8:51 dpdklab
2024-09-03  8:23 dpdklab
2024-09-03  7:40 dpdklab
2024-09-03  7:30 dpdklab
2024-09-03  7:29 dpdklab
2024-09-03  7:21 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=66d6c4aa.050a0220.ce24f.0586SMTPIN_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).