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] a1dff49b89249659bb40512bb1410a9afba0f382
Date: Wed, 17 Jan 2024 09:30:32 -0800 (PST)	[thread overview]
Message-ID: <65a80eb8.050a0220.2e764.b42eSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk-next-eventdev

a1dff49b89249659bb40512bb1410a9afba0f382 --> testing pass

Test environment and result as below:

+---------------------+--------------------+
|     Environment     | dpdk_meson_compile |
+=====================+====================+
| FreeBSD 13          | PASS               |
+---------------------+--------------------+
| Fedora 38           | PASS               |
+---------------------+--------------------+
| Debian Buster       | PASS               |
+---------------------+--------------------+
| Debian Bullseye     | PASS               |
+---------------------+--------------------+
| Windows Server 2022 | PASS               |
+---------------------+--------------------+
| Fedora 37           | PASS               |
+---------------------+--------------------+
| openSUSE Leap 15    | PASS               |
+---------------------+--------------------+
| Ubuntu 22.04        | PASS               |
+---------------------+--------------------+
| CentOS Stream 8     | PASS               |
+---------------------+--------------------+
| CentOS Stream 9     | PASS               |
+---------------------+--------------------+
| RHEL8               | PASS               |
+---------------------+--------------------+
| Windows Server 2019 | PASS               |
+---------------------+--------------------+
| Ubuntu 20.04        | PASS               |
+---------------------+--------------------+


FreeBSD 13
	Kernel: 13.0
	Compiler: clang 11.0.1

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

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

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

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

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

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

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

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

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

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/27693/

UNH-IOL DPDK Community Lab

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

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

Thread overview: 160+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-17 17:30 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-17 23:47 dpdklab
2024-01-17 23:40 dpdklab
2024-01-17 21:19 dpdklab
2024-01-17 20:10 dpdklab
2024-01-17 18:24 dpdklab
2024-01-17 18:02 dpdklab
2024-01-17 17:43 dpdklab
2024-01-17 17:37 dpdklab
2024-01-17 17:32 dpdklab
2024-01-17 17:31 dpdklab
2024-01-17 17:30 dpdklab
2024-01-17 17:30 dpdklab
2024-01-17 17:28 dpdklab
2024-01-17 17:28 dpdklab
2024-01-17 17:28 dpdklab
2024-01-17 17:26 dpdklab
2024-01-17 17:26 dpdklab
2024-01-17 17:25 dpdklab
2024-01-17 17:23 dpdklab
2024-01-17 17:23 dpdklab
2024-01-17 17:22 dpdklab
2024-01-17 17:21 dpdklab
2024-01-17 17:21 dpdklab
2024-01-17 17:21 dpdklab
2024-01-17 17:18 dpdklab
2024-01-17 17:18 dpdklab
2024-01-17 17:16 dpdklab
2024-01-17 17:14 dpdklab
2024-01-17 17:14 dpdklab
2024-01-17 17:14 dpdklab
2024-01-17 17:13 dpdklab
2024-01-17 17:13 dpdklab
2024-01-17 17:13 dpdklab
2024-01-17 17:11 dpdklab
2024-01-17 17:11 dpdklab
2024-01-17 17:11 dpdklab
2024-01-17 17:10 dpdklab
2024-01-17 17:10 dpdklab
2024-01-17 17:09 dpdklab
2024-01-17 17:08 dpdklab
2024-01-17 17:08 dpdklab
2024-01-17 17:06 dpdklab
2024-01-17 17:05 dpdklab
2024-01-17 16:50 dpdklab
2024-01-17 16:49 dpdklab
2024-01-17 16:49 dpdklab
2024-01-17 16:49 dpdklab
2024-01-17 16:46 dpdklab
2024-01-17 16:46 dpdklab
2024-01-17 16:46 dpdklab
2024-01-04 22:18 dpdklab
2024-01-04 22:10 dpdklab
2024-01-04  5:37 dpdklab
2024-01-04  1:00 dpdklab
2024-01-04  0:29 dpdklab
2024-01-04  0:25 dpdklab
2024-01-04  0:12 dpdklab
2024-01-03 23:54 dpdklab
2024-01-03 23:51 dpdklab
2024-01-03 23:11 dpdklab
2024-01-03 23:03 dpdklab
2024-01-03 22:59 dpdklab
2024-01-03 22:56 dpdklab
2024-01-03 22:54 dpdklab
2024-01-03 22:53 dpdklab
2024-01-03 22:52 dpdklab
2024-01-03 22:51 dpdklab
2024-01-03 22:51 dpdklab
2024-01-03 22:43 dpdklab
2024-01-03 22:43 dpdklab
2024-01-03 22:42 dpdklab
2024-01-03 22:42 dpdklab
2024-01-03 22:41 dpdklab
2024-01-03 22:41 dpdklab
2024-01-03 22:40 dpdklab
2024-01-03 22:40 dpdklab
2024-01-03 22:40 dpdklab
2024-01-03 22:39 dpdklab
2024-01-03 22:38 dpdklab
2024-01-03 22:37 dpdklab
2024-01-03 22:37 dpdklab
2024-01-03 22:37 dpdklab
2024-01-03 22:36 dpdklab
2024-01-03 22:36 dpdklab
2024-01-03 22:34 dpdklab
2024-01-03 22:33 dpdklab
2024-01-03 22:32 dpdklab
2024-01-03 22:32 dpdklab
2024-01-03 22:31 dpdklab
2024-01-03 22:31 dpdklab
2024-01-03 22:25 dpdklab
2024-01-03 22:22 dpdklab
2024-01-03 22:18 dpdklab
2024-01-03 22:17 dpdklab
2024-01-03 22:16 dpdklab
2024-01-03 22:15 dpdklab
2024-01-03 22:01 dpdklab
2024-01-03 21:59 dpdklab
2024-01-03 21:49 dpdklab
2024-01-03 21:49 dpdklab
2024-01-03 21:47 dpdklab
2024-01-03 20:55 dpdklab
2024-01-03 20:50 dpdklab
2024-01-03 20:41 dpdklab
2024-01-03 20:36 dpdklab
2024-01-03 20:36 dpdklab
2023-12-14 17:38 dpdklab
2023-12-14 17:33 dpdklab
2023-12-14 17:33 dpdklab
2023-12-14 16:19 dpdklab
2023-12-14 16:12 dpdklab
2023-12-14 16:08 dpdklab
2023-12-14 16:06 dpdklab
2023-12-14 16:01 dpdklab
2023-12-14 15:34 dpdklab
2023-12-14 15:30 dpdklab
2023-12-14 15:24 dpdklab
2023-12-14 15:21 dpdklab
2023-12-14 15:21 dpdklab
2023-12-14 15:00 dpdklab
2023-12-14 14:57 dpdklab
2023-12-14 14:57 dpdklab
2023-12-14 14:40 dpdklab
2023-12-14 14:39 dpdklab
2023-12-14 14:39 dpdklab
2023-12-14 14:35 dpdklab
2023-12-14 14:31 dpdklab
2023-12-14 14:30 dpdklab
2023-12-14 14:27 dpdklab
2023-12-14 14:26 dpdklab
2023-12-14 14:15 dpdklab
2023-12-14 14:14 dpdklab
2023-12-14 14:09 dpdklab
2023-12-14 14:08 dpdklab
2023-12-14 14:07 dpdklab
2023-12-14 14:07 dpdklab
2023-12-14 14:07 dpdklab
2023-12-14 14:04 dpdklab
2023-12-14 14:03 dpdklab
2023-12-14 14:02 dpdklab
2023-12-14 14:01 dpdklab
2023-12-14 13:55 dpdklab
2023-12-14 13:52 dpdklab
2023-12-14 13:52 dpdklab
2023-12-14 13:26 dpdklab
2023-12-14 13:03 dpdklab
2023-12-14 12:47 dpdklab
2023-12-14 12:41 dpdklab
2023-12-14 12:40 dpdklab
2023-12-14 12:39 dpdklab
2023-12-14 12:39 dpdklab
2023-12-14 12:36 dpdklab
2023-12-14 12:35 dpdklab
2023-12-14 12:27 dpdklab
2023-12-14 12:27 dpdklab
2023-12-14 12:27 dpdklab
2023-12-14 12:27 dpdklab
2023-12-14 12:24 dpdklab
2023-12-14 12:20 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=65a80eb8.050a0220.2e764.b42eSMTPIN_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).