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] 240fcef51bceb527c624a2329ca1e3030fbd64db
Date: Sat, 09 Mar 2024 22:11:18 -0800 (PST)	[thread overview]
Message-ID: <65ed4f06.050a0220.abd28.4197SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk-next-crypto

240fcef51bceb527c624a2329ca1e3030fbd64db --> testing pass

Test environment and result as below:

+--------------+----------------------+----------------------+
| Environment  | dpdk_fips_validation | compressdev_zlib_pmd |
+==============+======================+======================+
| Ubuntu 20.04 | PASS                 | SKIPPED              |
+--------------+----------------------+----------------------+
| Ubuntu 22.04 | SKIPPED              | PASS                 |
+--------------+----------------------+----------------------+


Ubuntu 20.04
	Kernel: 5.4.0-153-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

Ubuntu 22.04
	Kernel: 5.15.0-91-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/28327/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-03-10  6:12 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-10  6:11 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-10  5:30 dpdklab
2024-03-10  4:41 dpdklab
2024-03-05 23:27 dpdklab
2024-03-05 22:57 dpdklab
2024-03-05 22:34 dpdklab
2024-03-05 21:54 dpdklab
2024-03-05 21:53 dpdklab
2024-03-05 21:37 dpdklab
2024-03-05 21:31 dpdklab
2024-03-05 21:30 dpdklab
2024-03-05 21:30 dpdklab
2024-03-05 21:27 dpdklab
2024-03-05 21:26 dpdklab
2024-03-05 21:26 dpdklab
2024-03-05 21:24 dpdklab
2024-03-05 21:23 dpdklab
2024-03-05 21:23 dpdklab
2024-03-05 21:21 dpdklab
2024-03-05 21:21 dpdklab
2024-03-05 21:21 dpdklab
2024-03-05 21:20 dpdklab
2024-03-05 21:20 dpdklab
2024-03-05 21:19 dpdklab
2024-03-05 21:19 dpdklab
2024-03-05 21:17 dpdklab
2024-03-05 21:17 dpdklab
2024-03-05 21:17 dpdklab
2024-03-05 21:17 dpdklab
2024-03-05 21:17 dpdklab
2024-03-05 21:16 dpdklab
2024-03-05 21:16 dpdklab
2024-03-05 21:16 dpdklab
2024-03-05 21:16 dpdklab
2024-03-05 21:16 dpdklab
2024-03-05 21:16 dpdklab
2024-03-05 21:15 dpdklab
2024-03-05 21:15 dpdklab
2024-03-05 21:15 dpdklab
2024-03-05 21:15 dpdklab
2024-03-05 21:15 dpdklab
2024-03-05 21:14 dpdklab
2024-03-05 21:14 dpdklab
2024-03-05 21:14 dpdklab
2024-03-05 21:13 dpdklab
2024-03-05 21:13 dpdklab
2024-03-05 21:12 dpdklab
2024-03-05 21:12 dpdklab
2024-03-05 21:12 dpdklab
2024-03-05 21:11 dpdklab
2024-03-05 21:11 dpdklab
2024-03-05 21:11 dpdklab
2024-03-05 21:11 dpdklab
2024-03-05 21:10 dpdklab
2024-03-05 21:10 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=65ed4f06.050a0220.abd28.4197SMTPIN_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).