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, Xueming Li <xuemingl@nvidia.com>,
	Christian Ehrhardt <christian.ehrhardt@canonical.com>,
	Kevin Traynor <ktraynor@redhat.com>,
	Luca Boccassi <bluca@debian.org>
Subject: |SUCCESS| [GIT MASTER] 244dbbf778711898b21d07ddc78d9904e68a15d2
Date: Tue, 19 Mar 2024 23:16:48 -0700 (PDT)	[thread overview]
Message-ID: <65fa7f50.050a0220.15f11.d373SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: tags/v22.11

244dbbf778711898b21d07ddc78d9904e68a15d2 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| Windows Server 2022 | PASS           |
+---------------------+----------------+
| Fedora 37           | PASS           |
+---------------------+----------------+
| Debian 11 (arm)     | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| RHEL8               | PASS           |
+---------------------+----------------+


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

Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9

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

Debian 11 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

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

RHEL8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-03-20  6:16 UTC|newest]

Thread overview: 224+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-20  6:16 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-23 22:12 dpdklab
2024-03-23 20:04 dpdklab
2024-03-23  2:44 dpdklab
2024-03-23  1:57 dpdklab
2024-03-22  8:21 dpdklab
2024-03-22  7:02 dpdklab
2024-03-22  6:55 dpdklab
2024-03-22  6:54 dpdklab
2024-03-22  6:54 dpdklab
2024-03-22  6:53 dpdklab
2024-03-22  6:40 dpdklab
2024-03-22  6:22 dpdklab
2024-03-22  6:18 dpdklab
2024-03-22  6:16 dpdklab
2024-03-22  6:16 dpdklab
2024-03-22  6:12 dpdklab
2024-03-22  6:07 dpdklab
2024-03-22  6:02 dpdklab
2024-03-22  5:59 dpdklab
2024-03-22  5:55 dpdklab
2024-03-22  5:53 dpdklab
2024-03-22  5:53 dpdklab
2024-03-22  5:52 dpdklab
2024-03-22  5:50 dpdklab
2024-03-22  5:49 dpdklab
2024-03-22  5:47 dpdklab
2024-03-22  5:46 dpdklab
2024-03-22  5:44 dpdklab
2024-03-22  5:44 dpdklab
2024-03-22  5:43 dpdklab
2024-03-22  5:40 dpdklab
2024-03-22  5:38 dpdklab
2024-03-22  5:34 dpdklab
2024-03-22  5:32 dpdklab
2024-03-22  5:31 dpdklab
2024-03-22  5:31 dpdklab
2024-03-22  5:30 dpdklab
2024-03-22  5:27 dpdklab
2024-03-22  5:26 dpdklab
2024-03-22  5:22 dpdklab
2024-03-22  5:17 dpdklab
2024-03-22  5:16 dpdklab
2024-03-22  5:10 dpdklab
2024-03-22  5:09 dpdklab
2024-03-22  5:08 dpdklab
2024-03-22  5:08 dpdklab
2024-03-22  5:06 dpdklab
2024-03-22  5:05 dpdklab
2024-03-22  5:05 dpdklab
2024-03-22  5:04 dpdklab
2024-03-22  5:02 dpdklab
2024-03-22  5:02 dpdklab
2024-03-22  4:59 dpdklab
2024-03-22  4:59 dpdklab
2024-03-22  4:58 dpdklab
2024-03-22  4:58 dpdklab
2024-03-22  4:57 dpdklab
2024-03-21 22:57 dpdklab
2024-03-21 17:22 dpdklab
2024-03-21 16:34 dpdklab
2024-03-21 14:24 dpdklab
2024-03-21 14:20 dpdklab
2024-03-21 12:53 dpdklab
2024-03-21 12:48 dpdklab
2024-03-21 11:10 dpdklab
2024-03-21 11:09 dpdklab
2024-03-21 10:58 dpdklab
2024-03-21 10:41 dpdklab
2024-03-21 10:39 dpdklab
2024-03-21 10:08 dpdklab
2024-03-21  9:57 dpdklab
2024-03-21  9:47 dpdklab
2024-03-21  9:31 dpdklab
2024-03-21  9:28 dpdklab
2024-03-21  9:27 dpdklab
2024-03-21  9:23 dpdklab
2024-03-21  9:22 dpdklab
2024-03-21  9:20 dpdklab
2024-03-21  9:14 dpdklab
2024-03-21  9:13 dpdklab
2024-03-21  9:03 dpdklab
2024-03-21  9:03 dpdklab
2024-03-21  9:02 dpdklab
2024-03-21  9:00 dpdklab
2024-03-21  8:59 dpdklab
2024-03-21  8:59 dpdklab
2024-03-21  8:59 dpdklab
2024-03-21  8:58 dpdklab
2024-03-21  8:58 dpdklab
2024-03-21  8:57 dpdklab
2024-03-21  8:56 dpdklab
2024-03-21  8:55 dpdklab
2024-03-21  8:54 dpdklab
2024-03-21  8:53 dpdklab
2024-03-21  8:52 dpdklab
2024-03-21  8:49 dpdklab
2024-03-21  8:46 dpdklab
2024-03-21  8:46 dpdklab
2024-03-21  8:42 dpdklab
2024-03-21  7:37 dpdklab
2024-03-21  7:30 dpdklab
2024-03-21  7:28 dpdklab
2024-03-21  7:28 dpdklab
2024-03-21  7:27 dpdklab
2024-03-21  7:26 dpdklab
2024-03-21  7:11 dpdklab
2024-03-21  7:10 dpdklab
2024-03-21  7:10 dpdklab
2024-03-21  7:10 dpdklab
2024-03-21  7:09 dpdklab
2024-03-21  7:08 dpdklab
2024-03-21  6:44 dpdklab
2024-03-21  6:44 dpdklab
2024-03-21  6:36 dpdklab
2024-03-21  6:35 dpdklab
2024-03-21  6:32 dpdklab
2024-03-21  6:28 dpdklab
2024-03-21  3:23 dpdklab
2024-03-21  2:38 dpdklab
2024-03-20 22:49 dpdklab
2024-03-20  8:45 dpdklab
2024-03-20  8:09 dpdklab
2024-03-20  6:56 dpdklab
2024-03-20  6:56 dpdklab
2024-03-20  6:52 dpdklab
2024-03-20  6:50 dpdklab
2024-03-20  6:49 dpdklab
2024-03-20  6:49 dpdklab
2024-03-20  6:47 dpdklab
2024-03-20  6:43 dpdklab
2024-03-20  6:29 dpdklab
2024-03-20  6:22 dpdklab
2024-03-20  6:21 dpdklab
2024-03-20  6:14 dpdklab
2024-03-20  6:10 dpdklab
2024-03-20  6:09 dpdklab
2024-03-20  6:03 dpdklab
2024-03-20  6:01 dpdklab
2024-03-20  5:59 dpdklab
2024-03-20  5:55 dpdklab
2024-03-20  5:54 dpdklab
2024-03-20  5:54 dpdklab
2024-03-20  5:54 dpdklab
2024-03-20  5:53 dpdklab
2024-03-20  5:53 dpdklab
2024-03-20  5:51 dpdklab
2024-03-20  5:50 dpdklab
2024-03-20  5:49 dpdklab
2024-03-20  5:46 dpdklab
2024-03-20  5:44 dpdklab
2024-03-20  5:43 dpdklab
2024-03-20  5:28 dpdklab
2024-03-20  5:28 dpdklab
2024-03-20  5:23 dpdklab
2024-03-20  5:23 dpdklab
2024-03-20  5:12 dpdklab
2024-03-20  5:11 dpdklab
2024-03-20  5:10 dpdklab
2024-03-20  5:10 dpdklab
2024-03-20  5:01 dpdklab
2024-03-20  5:01 dpdklab
2024-03-20  4:58 dpdklab
2024-03-20  4:57 dpdklab
2024-03-20  4:49 dpdklab
2024-03-20  4:48 dpdklab
2024-03-20  4:47 dpdklab
2024-03-20  4:46 dpdklab
2024-03-20  4:31 dpdklab
2024-03-20  4:31 dpdklab
2024-03-20  4:28 dpdklab
2024-03-19  8:17 dpdklab
2024-03-19  8:04 dpdklab
2024-03-19  8:02 dpdklab
2024-03-19  7:44 dpdklab
2024-03-19  7:25 dpdklab
2024-03-19  6:32 dpdklab
2024-03-19  6:32 dpdklab
2024-03-19  6:31 dpdklab
2024-03-19  6:29 dpdklab
2024-03-19  6:26 dpdklab
2024-03-19  6:21 dpdklab
2024-03-19  6:16 dpdklab
2024-03-19  6:15 dpdklab
2024-03-19  6:13 dpdklab
2024-03-19  6:12 dpdklab
2024-03-19  6:11 dpdklab
2024-03-19  6:04 dpdklab
2024-03-19  6:02 dpdklab
2024-03-19  6:01 dpdklab
2024-03-19  6:00 dpdklab
2024-03-19  5:58 dpdklab
2024-03-19  5:56 dpdklab
2024-03-19  5:55 dpdklab
2024-03-19  5:55 dpdklab
2024-03-19  5:54 dpdklab
2024-03-19  5:54 dpdklab
2024-03-19  5:53 dpdklab
2024-03-19  5:49 dpdklab
2024-03-19  5:47 dpdklab
2024-03-19  5:47 dpdklab
2024-03-19  5:43 dpdklab
2024-03-19  5:42 dpdklab
2024-03-19  5:41 dpdklab
2024-03-19  5:38 dpdklab
2024-03-19  5:37 dpdklab
2024-03-19  5:31 dpdklab
2024-03-19  5:31 dpdklab
2024-03-19  5:31 dpdklab
2024-03-19  5:30 dpdklab
2024-03-19  5:26 dpdklab
2024-03-19  5:19 dpdklab
2024-03-19  5:18 dpdklab
2024-03-19  5:16 dpdklab
2024-03-19  5:14 dpdklab
2024-03-19  5:11 dpdklab
2024-03-19  5:09 dpdklab
2024-03-19  5:08 dpdklab
2024-03-19  5:07 dpdklab
2024-03-19  5:07 dpdklab
2024-03-19  5:07 dpdklab
2024-03-19  5:06 dpdklab
2024-03-19  5:05 dpdklab
2024-03-19  5:05 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=65fa7f50.050a0220.15f11.d373SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ktraynor@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=xuemingl@nvidia.com \
    /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).