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] 2186e618f1779515164766839c8dd14978548b79
Date: Thu, 14 Mar 2024 13:23:14 -0700 (PDT)	[thread overview]
Message-ID: <65f35cb2.810a0220.1c053.aafaSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk-next-crypto

2186e618f1779515164766839c8dd14978548b79 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Debian 12 (arm)     | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| Fedora 37           | PASS           |
+---------------------+----------------+
| Fedora 38           | PASS           |
+---------------------+----------------+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| Ubuntu 20.04        | PASS           |
+---------------------+----------------+


CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

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

Debian 12 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 11

Debian Bullseye
	Kernel: 5.4.0-122-generic
	Compiler: gcc 10.2.1-6

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-03-14 20:23 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-14 20:23 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-18 14:37 dpdklab
2024-03-18 13:57 dpdklab
2024-03-14 21:29 dpdklab
2024-03-14 20:56 dpdklab
2024-03-14 20:50 dpdklab
2024-03-14 20:47 dpdklab
2024-03-14 20:45 dpdklab
2024-03-14 20:44 dpdklab
2024-03-14 20:29 dpdklab
2024-03-14 20:29 dpdklab
2024-03-14 20:29 dpdklab
2024-03-14 20:29 dpdklab
2024-03-14 20:29 dpdklab
2024-03-14 20:29 dpdklab
2024-03-14 20:28 dpdklab
2024-03-14 20:27 dpdklab
2024-03-14 20:27 dpdklab
2024-03-14 20:27 dpdklab
2024-03-14 20:26 dpdklab
2024-03-14 20:26 dpdklab
2024-03-14 20:26 dpdklab
2024-03-14 20:26 dpdklab
2024-03-14 20:25 dpdklab
2024-03-14 20:25 dpdklab
2024-03-14 20:25 dpdklab
2024-03-14 20:25 dpdklab
2024-03-14 20:25 dpdklab
2024-03-14 20:23 dpdklab
2024-03-14 20:23 dpdklab
2024-03-14 20:23 dpdklab
2024-03-14 20:23 dpdklab
2024-03-14 20:22 dpdklab
2024-03-14 20:22 dpdklab
2024-03-14 20:22 dpdklab
2024-03-14 20:22 dpdklab
2024-03-14 20:19 dpdklab
2024-03-14 20:18 dpdklab
2024-03-14 20:18 dpdklab
2024-03-14 20:18 dpdklab
2024-03-14 20:18 dpdklab
2024-03-14 20:18 dpdklab
2024-03-14 20:17 dpdklab
2024-03-14 20:17 dpdklab
2024-03-14 20:17 dpdklab
2024-03-14 20:16 dpdklab
2024-03-14 20:16 dpdklab
2024-03-14 20:16 dpdklab
2024-03-14 20:16 dpdklab
2024-03-14 20:16 dpdklab
2024-03-14 20:16 dpdklab
2024-03-14 20:15 dpdklab
2024-03-14 20:15 dpdklab
2024-03-14 20:15 dpdklab
2024-03-14 20:15 dpdklab
2024-03-14 20:15 dpdklab
2024-03-14 20:14 dpdklab
2024-03-14 20:14 dpdklab
2024-03-14 20:14 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=65f35cb2.810a0220.1c053.aafaSMTPIN_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).