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, Jerin Jacob <jerinj@marvell.com>
Subject: |SUCCESS| [GIT MASTER] f51828c00c2c65786d4e2935b4295a524af1f217
Date: Mon, 04 Mar 2024 09:50:21 -0800 (PST)	[thread overview]
Message-ID: <65e609dd.050a0220.54754.1ee4SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk-next-eventdev

f51828c00c2c65786d4e2935b4295a524af1f217 --> testing pass

Test environment and result as below:

+---------------------+--------------------+
|     Environment     | dpdk_meson_compile |
+=====================+====================+
| FreeBSD 13.2        | PASS               |
+---------------------+--------------------+
| Windows Server 2022 | PASS               |
+---------------------+--------------------+
| CentOS Stream 9     | PASS               |
+---------------------+--------------------+
| Ubuntu 20.04        | PASS               |
+---------------------+--------------------+
| openSUSE Leap 15    | PASS               |
+---------------------+--------------------+
| CentOS Stream 8     | PASS               |
+---------------------+--------------------+
| RHEL8               | PASS               |
+---------------------+--------------------+
| Fedora 37           | PASS               |
+---------------------+--------------------+


FreeBSD 13.2
	Kernel: 13.2
	Compiler: clang 11.3.0

Windows Server 2022
	Kernel: OS Build 20348.2031
	Compiler: MSVC VS-Preview

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

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

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

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

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-03-04 17:50 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04 17:50 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-08  8:55 dpdklab
2024-03-08  8:06 dpdklab
2024-03-08  7:26 dpdklab
2024-03-04 20:27 dpdklab
2024-03-04 19:12 dpdklab
2024-03-04 19:11 dpdklab
2024-03-04 19:04 dpdklab
2024-03-04 18:47 dpdklab
2024-03-04 18:39 dpdklab
2024-03-04 18:38 dpdklab
2024-03-04 18:37 dpdklab
2024-03-04 18:37 dpdklab
2024-03-04 18:36 dpdklab
2024-03-04 18:36 dpdklab
2024-03-04 18:21 dpdklab
2024-03-04 18:21 dpdklab
2024-03-04 18:21 dpdklab
2024-03-04 18:14 dpdklab
2024-03-04 18:14 dpdklab
2024-03-04 18:13 dpdklab
2024-03-04 18:09 dpdklab
2024-03-04 18:09 dpdklab
2024-03-04 18:09 dpdklab
2024-03-04 18:08 dpdklab
2024-03-04 18:08 dpdklab
2024-03-04 18:06 dpdklab
2024-03-04 18:04 dpdklab
2024-03-04 18:03 dpdklab
2024-03-04 18:03 dpdklab
2024-03-04 18:03 dpdklab
2024-03-04 18:03 dpdklab
2024-03-04 18:02 dpdklab
2024-03-04 18:02 dpdklab
2024-03-04 18:02 dpdklab
2024-03-04 18:02 dpdklab
2024-03-04 18:01 dpdklab
2024-03-04 17:59 dpdklab
2024-03-04 17:59 dpdklab
2024-03-04 17:58 dpdklab
2024-03-04 17:55 dpdklab
2024-03-04 17:55 dpdklab
2024-03-04 17:55 dpdklab
2024-03-04 17:53 dpdklab
2024-03-04 17:52 dpdklab
2024-03-04 17:52 dpdklab
2024-03-04 17:51 dpdklab
2024-03-04 17:51 dpdklab
2024-03-04 17:50 dpdklab
2024-03-04 17:50 dpdklab
2024-03-04 17:49 dpdklab
2024-03-04 17:48 dpdklab
2024-03-04 17:48 dpdklab
2024-03-04 17:48 dpdklab
2024-03-04 17:48 dpdklab
2024-03-04 17:48 dpdklab
2024-03-04 17:47 dpdklab
2024-03-04 17:47 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=65e609dd.050a0220.54754.1ee4SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=jerinj@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).