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] 3b80379078a1f7c09b8d0ece24442c8ff2e2c67c
Date: Thu, 27 Jun 2024 18:39:50 -0700 (PDT)	[thread overview]
Message-ID: <667e1466.050a0220.34666.22a5SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk-next-crypto

3b80379078a1f7c09b8d0ece24442c8ff2e2c67c --> testing pass

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-06-28  1:39 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-28  1:39 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-29  5:34 dpdklab
2024-06-29  3:28 dpdklab
2024-06-29  2:18 dpdklab
2024-06-28  8:45 dpdklab
2024-06-28  8:39 dpdklab
2024-06-28  8:27 dpdklab
2024-06-28  8:22 dpdklab
2024-06-28  8:17 dpdklab
2024-06-28  8:11 dpdklab
2024-06-28  8:08 dpdklab
2024-06-28  7:51 dpdklab
2024-06-28  7:44 dpdklab
2024-06-28  7:30 dpdklab
2024-06-28  7:22 dpdklab
2024-06-28  7:20 dpdklab
2024-06-28  7:14 dpdklab
2024-06-28  7:14 dpdklab
2024-06-28  7:11 dpdklab
2024-06-28  6:49 dpdklab
2024-06-28  6:26 dpdklab
2024-06-28  6:20 dpdklab
2024-06-28  6:14 dpdklab
2024-06-28  6:06 dpdklab
2024-06-28  6:02 dpdklab
2024-06-28  5:57 dpdklab
2024-06-28  5:56 dpdklab
2024-06-28  5:36 dpdklab
2024-06-28  5:33 dpdklab
2024-06-28  5:20 dpdklab
2024-06-28  5:18 dpdklab
2024-06-28  5:03 dpdklab
2024-06-28  4:54 dpdklab
2024-06-28  4:53 dpdklab
2024-06-28  4:43 dpdklab
2024-06-28  4:40 dpdklab
2024-06-28  4:39 dpdklab
2024-06-28  4:28 dpdklab
2024-06-28  4:25 dpdklab
2024-06-28  4:25 dpdklab
2024-06-28  4:24 dpdklab
2024-06-28  4:23 dpdklab
2024-06-28  4:21 dpdklab
2024-06-28  4:19 dpdklab
2024-06-28  4:17 dpdklab
2024-06-28  4:16 dpdklab
2024-06-28  4:15 dpdklab
2024-06-28  4:14 dpdklab
2024-06-28  4:11 dpdklab
2024-06-28  4:10 dpdklab
2024-06-28  4:04 dpdklab
2024-06-28  4:04 dpdklab
2024-06-28  4:01 dpdklab
2024-06-28  4:01 dpdklab
2024-06-28  3:59 dpdklab
2024-06-28  3:58 dpdklab
2024-06-28  3:56 dpdklab
2024-06-28  3:55 dpdklab
2024-06-28  3:55 dpdklab
2024-06-28  3:55 dpdklab
2024-06-28  3:54 dpdklab
2024-06-28  3:51 dpdklab
2024-06-28  3:48 dpdklab
2024-06-28  3:45 dpdklab
2024-06-28  3:45 dpdklab
2024-06-28  3:45 dpdklab
2024-06-28  3:43 dpdklab
2024-06-28  3:42 dpdklab
2024-06-28  3:38 dpdklab
2024-06-28  3:33 dpdklab
2024-06-28  3:26 dpdklab
2024-06-28  3:21 dpdklab
2024-06-28  3:17 dpdklab
2024-06-28  1:03 dpdklab
2024-06-28  0:55 dpdklab
2024-06-28  0:52 dpdklab
2024-06-27 23:23 dpdklab
2024-06-27 22:41 dpdklab
2024-06-27 22:41 dpdklab
2024-06-27 22:41 dpdklab
2024-06-27 22:38 dpdklab
2024-06-27 22:37 dpdklab
2024-06-27 22:34 dpdklab
2024-06-27 21:44 dpdklab
2024-06-27 21:30 dpdklab
2024-06-27 21:26 dpdklab
2024-06-27 21:23 dpdklab
2024-06-27 21:06 dpdklab
2024-06-27 21:03 dpdklab
2024-06-27 20:52 dpdklab
2024-06-27 20:48 dpdklab
2024-06-27 20:47 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=667e1466.050a0220.34666.22a5SMTPIN_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).