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] 22ce39b3aadb109cbefabb91aad44c94e8c2a5e6
Date: Thu, 20 Jun 2024 01:02:20 -0700 (PDT)	[thread overview]
Message-ID: <6673e20c.170a0220.64013.8696SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk

22ce39b3aadb109cbefabb91aad44c94e8c2a5e6 --> testing pass

Test environment and result as below:

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


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

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 Bullseye
	Kernel: 5.4.0-167-generic
	Compiler: gcc 10.2.1-6

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

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

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 38
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Fedora 40
	Kernel: Depends on container host
	Compiler: gcc 14.1.1

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1

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

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-06-20  8:02 UTC|newest]

Thread overview: 99+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-20  8:02 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-22  0:44 dpdklab
2024-06-20 16:03 dpdklab
2024-06-20 15:46 dpdklab
2024-06-20 12:20 dpdklab
2024-06-20 10:22 dpdklab
2024-06-20 10:21 dpdklab
2024-06-20 10:20 dpdklab
2024-06-20 10:19 dpdklab
2024-06-20 10:18 dpdklab
2024-06-20 10:17 dpdklab
2024-06-20 10:17 dpdklab
2024-06-20 10:11 dpdklab
2024-06-20 10:07 dpdklab
2024-06-20 10:06 dpdklab
2024-06-20 10:05 dpdklab
2024-06-20 10:01 dpdklab
2024-06-20  9:57 dpdklab
2024-06-20  9:57 dpdklab
2024-06-20  9:56 dpdklab
2024-06-20  9:56 dpdklab
2024-06-20  9:56 dpdklab
2024-06-20  9:54 dpdklab
2024-06-20  9:53 dpdklab
2024-06-20  9:53 dpdklab
2024-06-20  9:45 dpdklab
2024-06-20  9:40 dpdklab
2024-06-20  9:36 dpdklab
2024-06-20  9:36 dpdklab
2024-06-20  9:33 dpdklab
2024-06-20  9:33 dpdklab
2024-06-20  9:29 dpdklab
2024-06-20  9:29 dpdklab
2024-06-20  9:28 dpdklab
2024-06-20  9:27 dpdklab
2024-06-20  9:26 dpdklab
2024-06-20  9:20 dpdklab
2024-06-20  9:20 dpdklab
2024-06-20  9:10 dpdklab
2024-06-20  9:10 dpdklab
2024-06-20  9:09 dpdklab
2024-06-20  9:08 dpdklab
2024-06-20  9:06 dpdklab
2024-06-20  9:04 dpdklab
2024-06-20  9:02 dpdklab
2024-06-20  9:01 dpdklab
2024-06-20  8:55 dpdklab
2024-06-20  8:51 dpdklab
2024-06-20  8:48 dpdklab
2024-06-20  8:48 dpdklab
2024-06-20  8:45 dpdklab
2024-06-20  8:44 dpdklab
2024-06-20  8:44 dpdklab
2024-06-20  8:43 dpdklab
2024-06-20  8:42 dpdklab
2024-06-20  8:42 dpdklab
2024-06-20  8:41 dpdklab
2024-06-20  8:25 dpdklab
2024-06-20  8:23 dpdklab
2024-06-20  8:21 dpdklab
2024-06-20  8:17 dpdklab
2024-06-20  8:09 dpdklab
2024-06-20  8:06 dpdklab
2024-06-20  8:05 dpdklab
2024-06-20  7:41 dpdklab
2024-06-20  7:39 dpdklab
2024-06-20  7:38 dpdklab
2024-06-20  7:38 dpdklab
2024-06-20  7:37 dpdklab
2024-06-20  7:35 dpdklab
2024-06-20  7:34 dpdklab
2024-06-20  7:33 dpdklab
2024-06-20  7:32 dpdklab
2024-06-20  7:30 dpdklab
2024-06-20  5:51 dpdklab
2024-06-20  4:31 dpdklab
2024-06-20  4:30 dpdklab
2024-06-20  4:27 dpdklab
2024-06-20  4:07 dpdklab
2024-06-20  4:04 dpdklab
2024-06-20  4:03 dpdklab
2024-06-20  4:03 dpdklab
2024-06-20  4:01 dpdklab
2024-06-20  3:51 dpdklab
2024-06-20  3:41 dpdklab
2024-06-20  3:02 dpdklab
2024-06-20  3:01 dpdklab
2024-06-20  3:01 dpdklab
2024-06-20  2:59 dpdklab
2024-06-20  2:58 dpdklab
2024-06-20  2:39 dpdklab
2024-06-20  2:39 dpdklab
2024-06-20  2:36 dpdklab
2024-06-20  2:34 dpdklab
2024-06-20  2:32 dpdklab
2024-06-20  2:32 dpdklab
2024-06-20  2:31 dpdklab
2024-06-20  2:29 dpdklab
2024-06-20  2:25 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=6673e20c.170a0220.64013.8696SMTPIN_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).