automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 4352a3bcee3a4cc20c8accb71d683d5add3c6f80
Date: Fri, 10 Mar 2023 00:24:21 +0000 (UTC)	[thread overview]
Message-ID: <20230310002421.B01336011E@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

_Testing PASS_

Branch: dpdk-next-eventdev

4352a3bcee3a4cc20c8accb71d683d5add3c6f80 --> testing pass

Test environment and result as below:

+------------------+----------------+
|   Environment    | dpdk_unit_test |
+==================+================+
| Ubuntu 22.04     | PASS           |
+------------------+----------------+
| CentOS Stream 9  | PASS           |
+------------------+----------------+
| Debian Bullseye  | PASS           |
+------------------+----------------+
| Debian Buster    | PASS           |
+------------------+----------------+
| CentOS Stream 8  | PASS           |
+------------------+----------------+
| openSUSE Leap 15 | PASS           |
+------------------+----------------+
| Ubuntu 20.04     | PASS           |
+------------------+----------------+
| RHEL 7           | PASS           |
+------------------+----------------+
| RHEL8            | PASS           |
+------------------+----------------+


Ubuntu 22.04
	Kernel: Container Host Kernel
	Compiler: clang 14.0.5-1.fc36

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

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

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

openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0

Ubuntu 20.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.0-17ubuntu1~20.04

RHEL 7
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)

RHEL8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-03-10  0:24 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-10  0:24 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-09 17:06 dpdklab
2023-03-09 16:09 dpdklab
2023-03-09 15:53 dpdklab
2023-03-09 15:52 dpdklab
2023-03-09 15:36 dpdklab
2023-03-09 15:14 dpdklab
2023-03-09 15:09 dpdklab
2023-03-09 14:57 dpdklab
2023-03-09 14:55 dpdklab
2023-03-09 14:53 dpdklab
2023-03-09 14:43 dpdklab
2023-03-09 14:28 dpdklab
2023-03-09 14:26 dpdklab
2023-03-09 14:23 dpdklab
2023-03-09 14:23 dpdklab
2023-03-09 14:21 dpdklab
2023-03-09 13:38 dpdklab
2023-03-09 12:59 dpdklab
2023-03-09 12:52 dpdklab
2023-03-09 12:43 dpdklab
2023-03-09 12:40 dpdklab
2023-03-09 12:39 dpdklab
2023-03-09 12:39 dpdklab
2023-03-09 12:34 dpdklab
2023-03-09 12:29 dpdklab
2023-03-09 12:28 dpdklab
2023-03-09 12:26 dpdklab
2023-03-09 12:23 dpdklab
2023-03-09 12:23 dpdklab
2023-03-09 12:21 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=20230310002421.B01336011E@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --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).