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] 77e63757d2a0106a0cc519f5a82e2d749d16475a
Date: Mon, 27 May 2024 09:57:46 -0700 (PDT)	[thread overview]
Message-ID: <6654bb8a.050a0220.1afb6.790dSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk-next-eventdev

77e63757d2a0106a0cc519f5a82e2d749d16475a --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Debian 12           | PASS           |
+---------------------+----------------+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| Fedora 37           | PASS           |
+---------------------+----------------+
| Fedora 38           | PASS           |
+---------------------+----------------+


CentOS Stream 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

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

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-05-27 16:57 UTC|newest]

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