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, Akhil Goyal <gakhil@marvell.com>
Subject: |SUCCESS| [GIT MASTER] 69341a9deda8cd39e059ea7addb604612780612c
Date: Thu, 18 Jul 2024 13:28:27 -0700 (PDT)	[thread overview]
Message-ID: <66997aeb.810a0220.bf40c.01abSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk-next-crypto

69341a9deda8cd39e059ea7addb604612780612c --> testing pass

Upstream job id: Template-DTS-Pipeline#168908

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-07-18 20:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-18 20:28 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-18 23:44 dpdklab
2024-07-18 21:44 dpdklab
2024-07-18 21:04 dpdklab
2024-07-18 21:01 dpdklab
2024-07-18 20:58 dpdklab
2024-07-18 20:55 dpdklab
2024-07-18 20:54 dpdklab
2024-07-18 20:51 dpdklab
2024-07-18 20:50 dpdklab
2024-07-18 20:46 dpdklab
2024-07-18 20:43 dpdklab
2024-07-18 20:38 dpdklab
2024-07-18 20:33 dpdklab
2024-07-18 20:32 dpdklab
2024-07-18 20:28 dpdklab
2024-07-18 20:24 dpdklab
2024-07-18 20:16 dpdklab
2024-07-18 20:14 dpdklab
2024-07-18 20:09 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=66997aeb.810a0220.bf40c.01abSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=gakhil@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).