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,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| [GIT MASTER] f4ccce58c1a33cb41e1e820da504698437987efc
Date: Thu, 21 Nov 2024 00:47:37 -0800 (PST)	[thread overview]
Message-ID: <673ef3a9.170a0220.2e2ddb.297bSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk-next-net

f4ccce58c1a33cb41e1e820da504698437987efc --> testing pass

Upstream job id: Generic-Unit-Test-DPDK#293701

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Fedora 39           | PASS           |
+---------------------+----------------+
| Debian 12           | PASS           |
+---------------------+----------------+
| RHEL8               | PASS           |
+---------------------+----------------+
| Fedora 39 (Clang)   | PASS           |
+---------------------+----------------+
| RHEL9               | PASS           |
+---------------------+----------------+
| Fedora 40           | PASS           |
+---------------------+----------------+
| Fedora 40 (Clang)   | PASS           |
+---------------------+----------------+
| Ubuntu 22.04        | PASS           |
+---------------------+----------------+
| Ubuntu 20.04        | PASS           |
+---------------------+----------------+
| Ubuntu 24.04        | PASS           |
+---------------------+----------------+
| Windows Server 2022 | PASS           |
+---------------------+----------------+


CentOS Stream 9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)

Fedora 39
	Kernel: Depends on container host
	Compiler: gcc 13.3.1 20240522 (Red Hat 13.3.1-1)

Debian 12
	Kernel: Depends on container host
	Compiler: gcc (Debian 12.2.0-14) 12.2.0

RHEL8
	Kernel: Depends on container host
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-22)

Fedora 39 (Clang)
	Kernel: Depends on container host
	Compiler: clang 17.0.6 (Fedora 17.0.6-2.fc39)

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)

Fedora 40
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240801 (Red Hat 14.2.1-1)

Fedora 40 (Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.6 (Fedora 18.1.6-3.fc40)

Ubuntu 22.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Ubuntu 20.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

Ubuntu 24.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-11-21  8:47 UTC|newest]

Thread overview: 102+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-21  8:47 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-24  2:23 dpdklab
2024-11-24  2:20 dpdklab
2024-11-24  1:53 dpdklab
2024-11-24  1:42 dpdklab
2024-11-24  1:42 dpdklab
2024-11-24  1:28 dpdklab
2024-11-24  1:28 dpdklab
2024-11-24  1:24 dpdklab
2024-11-22 21:15 dpdklab
2024-11-22 19:38 dpdklab
2024-11-22 19:19 dpdklab
2024-11-22 19:19 dpdklab
2024-11-22 19:14 dpdklab
2024-11-22 19:09 dpdklab
2024-11-22 18:56 dpdklab
2024-11-22 18:56 dpdklab
2024-11-22 18:37 dpdklab
2024-11-22 18:22 dpdklab
2024-11-22 18:18 dpdklab
2024-11-22 17:52 dpdklab
2024-11-21 23:58 dpdklab
2024-11-21 23:49 dpdklab
2024-11-21 23:47 dpdklab
2024-11-21 23:41 dpdklab
2024-11-21 23:39 dpdklab
2024-11-21 23:11 dpdklab
2024-11-21 23:09 dpdklab
2024-11-21 22:58 dpdklab
2024-11-21 22:58 dpdklab
2024-11-21 22:55 dpdklab
2024-11-21 22:49 dpdklab
2024-11-21 22:46 dpdklab
2024-11-21 22:12 dpdklab
2024-11-21 21:55 dpdklab
2024-11-21 21:45 dpdklab
2024-11-21 21:37 dpdklab
2024-11-21 21:25 dpdklab
2024-11-21 21:18 dpdklab
2024-11-21 21:10 dpdklab
2024-11-21 21:10 dpdklab
2024-11-21 21:01 dpdklab
2024-11-21 20:43 dpdklab
2024-11-21 20:40 dpdklab
2024-11-21 20:19 dpdklab
2024-11-21 20:14 dpdklab
2024-11-21 20:14 dpdklab
2024-11-21 20:05 dpdklab
2024-11-21 19:50 dpdklab
2024-11-21 19:49 dpdklab
2024-11-21 19:46 dpdklab
2024-11-21 19:39 dpdklab
2024-11-21 19:38 dpdklab
2024-11-21 19:33 dpdklab
2024-11-21 19:30 dpdklab
2024-11-21 19:22 dpdklab
2024-11-21 19:22 dpdklab
2024-11-21 19:04 dpdklab
2024-11-21 18:58 dpdklab
2024-11-21 18:52 dpdklab
2024-11-21 18:44 dpdklab
2024-11-21 18:41 dpdklab
2024-11-21 18:39 dpdklab
2024-11-21 18:37 dpdklab
2024-11-21 18:31 dpdklab
2024-11-21 18:29 dpdklab
2024-11-21 18:23 dpdklab
2024-11-21 18:21 dpdklab
2024-11-21 18:21 dpdklab
2024-11-21 18:19 dpdklab
2024-11-21 18:16 dpdklab
2024-11-21 18:08 dpdklab
2024-11-21 18:01 dpdklab
2024-11-21 17:58 dpdklab
2024-11-21 17:54 dpdklab
2024-11-21 17:52 dpdklab
2024-11-21 17:50 dpdklab
2024-11-21 17:43 dpdklab
2024-11-21 15:06 dpdklab
2024-11-21 12:47 dpdklab
2024-11-21 12:43 dpdklab
2024-11-21 12:43 dpdklab
2024-11-21 12:39 dpdklab
2024-11-21 12:28 dpdklab
2024-11-21 12:26 dpdklab
2024-11-21 12:19 dpdklab
2024-11-21 12:16 dpdklab
2024-11-21 12:07 dpdklab
2024-11-21 12:03 dpdklab
2024-11-21 12:02 dpdklab
2024-11-21  9:56 dpdklab
2024-11-21  9:46 dpdklab
2024-11-21  9:09 dpdklab
2024-11-21  8:48 dpdklab
2024-11-21  8:46 dpdklab
2024-11-21  8:24 dpdklab
2024-11-21  8:23 dpdklab
2024-11-21  8:16 dpdklab
2024-11-21  8:10 dpdklab
2024-11-21  8:01 dpdklab
2024-11-21  7:58 dpdklab
2024-11-21  7:52 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=673ef3a9.170a0220.2e2ddb.297bSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ferruh.yigit@amd.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).