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] 92d74810cbdc4c04045d6a47dc3d867f1fa22de1
Date: Thu, 12 Oct 2023 10:04:01 -0700 (PDT)	[thread overview]
Message-ID: <65282701.250a0220.31793.0cb3SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk-next-crypto

92d74810cbdc4c04045d6a47dc3d867f1fa22de1 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Windows Server 2019 | PASS           |
+---------------------+----------------+


CentOS Stream 9
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.1 20220421

Windows Server 2019
	Kernel: 10.0
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/26453/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-10-12 17:04 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-12 17:04 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-13  2:19 dpdklab
2023-10-12 18:36 dpdklab
2023-10-12 18:35 dpdklab
2023-10-12 18:34 dpdklab
2023-10-12 18:20 dpdklab
2023-10-12 18:18 dpdklab
2023-10-12 18:17 dpdklab
2023-10-12 18:16 dpdklab
2023-10-12 18:12 dpdklab
2023-10-12 18:11 dpdklab
2023-10-12 18:11 dpdklab
2023-10-12 17:47 dpdklab
2023-10-12 17:46 dpdklab
2023-10-12 17:43 dpdklab
2023-10-12 17:37 dpdklab
2023-10-12 17:33 dpdklab
2023-10-12 17:31 dpdklab
2023-10-12 17:31 dpdklab
2023-10-12 17:29 dpdklab
2023-10-12 17:28 dpdklab
2023-10-12 17:27 dpdklab
2023-10-12 17:25 dpdklab
2023-10-12 17:24 dpdklab
2023-10-12 17:23 dpdklab
2023-10-12 17:15 dpdklab
2023-10-12 17:14 dpdklab
2023-10-12 17:10 dpdklab
2023-10-12 17:07 dpdklab
2023-10-12 17:02 dpdklab
2023-10-12 16:58 dpdklab
2023-10-12 16:57 dpdklab
2023-10-12 16:57 dpdklab
2023-10-12 16:57 dpdklab
2023-10-12 16:56 dpdklab
2023-10-12 16:55 dpdklab
2023-10-12 16:53 dpdklab
2023-10-12 16:52 dpdklab
2023-10-12 16:52 dpdklab
2023-10-12 16:51 dpdklab
2023-10-12 16:50 dpdklab
2023-10-12 16:26 dpdklab
2023-10-12 16:23 dpdklab
2023-10-12 16:23 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=65282701.250a0220.31793.0cb3SMTPIN_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).