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
Subject: |SUCCESS| [GIT MASTER] 85e327081f0649c0965e53f675ac3b55eb8be6db
Date: Wed, 12 Jun 2024 20:07:28 -0700 (PDT)	[thread overview]
Message-ID: <666a6270.050a0220.17755.19a5SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk

85e327081f0649c0965e53f675ac3b55eb8be6db --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| Arch Linux          | PASS           |
+---------------------+----------------+
| Fedora 39           | PASS           |
+---------------------+----------------+
| Fedora 37           | PASS           |
+---------------------+----------------+
| Fedora 38           | PASS           |
+---------------------+----------------+
| Debian 12           | PASS           |
+---------------------+----------------+
| openSUSE Leap 15    | PASS           |
+---------------------+----------------+
| RHEL9               | PASS           |
+---------------------+----------------+
| Windows Server 2022 | PASS           |
+---------------------+----------------+
| RHEL8               | PASS           |
+---------------------+----------------+
| Ubuntu 20.04        | PASS           |
+---------------------+----------------+
| Ubuntu 22.04        | PASS           |
+---------------------+----------------+
| Ubuntu 24.04        | PASS           |
+---------------------+----------------+


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

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

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

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

Arch Linux
	Kernel: 5.4.0-167-generic
	Compiler: gcc 14.1.1

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

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

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

openSUSE Leap 15
	Kernel: 5.4.0-167-generic
	Compiler: gcc 7.5.0

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1

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

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

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

Ubuntu 22.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.0

Ubuntu 24.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 13.2.0

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-06-13  3:07 UTC|newest]

Thread overview: 96+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13  3:07 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-13  5:10 dpdklab
2024-06-13  3:13 dpdklab
2024-06-13  3:13 dpdklab
2024-06-13  3:13 dpdklab
2024-06-13  3:13 dpdklab
2024-06-13  3:13 dpdklab
2024-06-13  3:12 dpdklab
2024-06-13  3:12 dpdklab
2024-06-13  3:12 dpdklab
2024-06-13  3:12 dpdklab
2024-06-13  3:11 dpdklab
2024-06-13  3:11 dpdklab
2024-06-13  3:11 dpdklab
2024-06-13  3:11 dpdklab
2024-06-13  3:10 dpdklab
2024-06-13  3:10 dpdklab
2024-06-13  3:10 dpdklab
2024-06-13  3:10 dpdklab
2024-06-13  3:09 dpdklab
2024-06-13  3:09 dpdklab
2024-06-13  3:09 dpdklab
2024-06-13  3:09 dpdklab
2024-06-13  3:09 dpdklab
2024-06-13  3:09 dpdklab
2024-06-13  3:08 dpdklab
2024-06-13  3:08 dpdklab
2024-06-13  3:08 dpdklab
2024-06-13  3:08 dpdklab
2024-06-13  3:08 dpdklab
2024-06-13  3:07 dpdklab
2024-06-13  3:07 dpdklab
2024-06-13  3:07 dpdklab
2024-06-13  3:07 dpdklab
2024-06-13  3:06 dpdklab
2024-06-13  3:06 dpdklab
2024-06-13  3:05 dpdklab
2024-06-13  3:04 dpdklab
2024-06-13  3:03 dpdklab
2024-06-13  3:02 dpdklab
2024-06-13  3:02 dpdklab
2024-06-13  3:02 dpdklab
2024-06-13  3:01 dpdklab
2024-06-13  3:01 dpdklab
2024-06-13  3:00 dpdklab
2024-06-13  2:58 dpdklab
2024-06-13  2:56 dpdklab
2024-06-13  2:54 dpdklab
2024-06-13  2:53 dpdklab
2024-06-13  2:52 dpdklab
2024-06-13  2:51 dpdklab
2024-06-13  2:50 dpdklab
2024-06-13  2:50 dpdklab
2024-06-13  2:50 dpdklab
2024-06-13  2:49 dpdklab
2024-06-13  2:49 dpdklab
2024-06-13  1:53 dpdklab
2024-06-13  1:32 dpdklab
2024-06-13  1:31 dpdklab
2024-06-13  1:31 dpdklab
2024-06-13  1:31 dpdklab
2024-06-13  1:31 dpdklab
2024-06-13  1:31 dpdklab
2024-06-13  1:31 dpdklab
2024-06-13  1:31 dpdklab
2024-06-13  1:31 dpdklab
2024-06-13  1:31 dpdklab
2024-06-13  1:31 dpdklab
2024-06-13  1:31 dpdklab
2024-06-13  1:31 dpdklab
2024-06-13  1:30 dpdklab
2024-06-13  1:30 dpdklab
2024-06-13  1:30 dpdklab
2024-06-13  1:30 dpdklab
2024-06-13  1:30 dpdklab
2024-06-13  1:30 dpdklab
2024-06-13  1:30 dpdklab
2024-06-13  1:30 dpdklab
2024-06-13  1:30 dpdklab
2024-06-13  1:29 dpdklab
2024-06-13  1:29 dpdklab
2024-06-13  1:29 dpdklab
2024-06-13  1:29 dpdklab
2024-06-13  1:29 dpdklab
2024-06-13  1:29 dpdklab
2024-06-13  1:29 dpdklab
2024-06-13  1:29 dpdklab
2024-06-13  1:28 dpdklab
2024-06-13  1:28 dpdklab
2024-06-13  1:28 dpdklab
2024-06-12  0:38 dpdklab
2024-06-12  0:36 dpdklab
2024-06-12  0:35 dpdklab
2024-06-12  0:34 dpdklab
2024-06-12  0:33 dpdklab
2024-06-12  0:30 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=666a6270.050a0220.17755.19a5SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@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).