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] 30a988126ecee65a890a4b6a52690442024f2554
Date: Fri, 19 Jan 2024 09:51:48 -0800 (PST)	[thread overview]
Message-ID: <65aab6b4.810a0220.a09f3.c140SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk-next-crypto

30a988126ecee65a890a4b6a52690442024f2554 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| Debian Buster       | PASS           |
+---------------------+----------------+
| Fedora 38           | PASS           |
+---------------------+----------------+
| Ubuntu 20.04        | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Ubuntu 22.04        | PASS           |
+---------------------+----------------+


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

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

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

Debian Buster
	Kernel: 5.4.0-122-generic
	Compiler: gcc 8.3.0-6

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

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

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

Ubuntu 22.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.0

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-19 17:51 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-19 17:51 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-22 15:21 dpdklab
2024-01-22 15:14 dpdklab
2024-01-20  8:09 dpdklab
2024-01-19 20:52 dpdklab
2024-01-19 20:51 dpdklab
2024-01-19 19:40 dpdklab
2024-01-19 19:33 dpdklab
2024-01-19 19:24 dpdklab
2024-01-19 19:23 dpdklab
2024-01-19 19:17 dpdklab
2024-01-19 19:15 dpdklab
2024-01-19 19:14 dpdklab
2024-01-19 19:14 dpdklab
2024-01-19 18:57 dpdklab
2024-01-19 18:57 dpdklab
2024-01-19 18:57 dpdklab
2024-01-19 18:55 dpdklab
2024-01-19 18:54 dpdklab
2024-01-19 18:53 dpdklab
2024-01-19 18:49 dpdklab
2024-01-19 18:49 dpdklab
2024-01-19 18:49 dpdklab
2024-01-19 18:45 dpdklab
2024-01-19 18:45 dpdklab
2024-01-19 18:38 dpdklab
2024-01-19 18:38 dpdklab
2024-01-19 18:38 dpdklab
2024-01-19 18:38 dpdklab
2024-01-19 18:37 dpdklab
2024-01-19 18:37 dpdklab
2024-01-19 18:36 dpdklab
2024-01-19 18:35 dpdklab
2024-01-19 18:35 dpdklab
2024-01-19 18:34 dpdklab
2024-01-19 18:34 dpdklab
2024-01-19 18:32 dpdklab
2024-01-19 18:27 dpdklab
2024-01-19 18:25 dpdklab
2024-01-19 18:25 dpdklab
2024-01-19 18:19 dpdklab
2024-01-19 18:17 dpdklab
2024-01-19 18:04 dpdklab
2024-01-19 18:02 dpdklab
2024-01-19 17:56 dpdklab
2024-01-19 17:34 dpdklab
2024-01-19 17:21 dpdklab
2024-01-19 17:20 dpdklab
2024-01-19 17:00 dpdklab
2024-01-19 17:00 dpdklab
2024-01-19 16:23 dpdklab
2024-01-19 16:22 dpdklab
2024-01-19 16:21 dpdklab
2024-01-19 16:21 dpdklab
2024-01-19 16:19 dpdklab
2024-01-19 16:19 dpdklab
2024-01-19 16:18 dpdklab
2024-01-19 16:18 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=65aab6b4.810a0220.a09f3.c140SMTPIN_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).