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] 7df61db6c387703a36306c1aea92225921e2eeb2
Date: Fri, 13 Dec 2024 14:05:29 -0800 (PST)	[thread overview]
Message-ID: <675cafa9.050a0220.342e79.0c07SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk

7df61db6c387703a36306c1aea92225921e2eeb2 --> testing pass

Upstream job id: Generic-VM-Unit-Test-DPDK#26580

Test environment and result as below:

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


Arch Linux
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240805

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

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

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

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

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

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

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

Ubuntu 22.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.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/31904/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-12-13 22:05 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-13 22:05 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-13 22:26 dpdklab
2024-12-13 21:54 dpdklab
2024-12-13 21:02 dpdklab
2024-12-13 20:04 dpdklab
2024-12-13 20:02 dpdklab
2024-12-13 18:10 dpdklab
2024-12-13 15:53 dpdklab
2024-12-13 11:52 dpdklab
2024-12-13 10:44 dpdklab
2024-12-13 10:07 dpdklab
2024-12-13 10:04 dpdklab
2024-12-13  9:47 dpdklab
2024-12-13  9:40 dpdklab
2024-12-13  9:33 dpdklab
2024-12-13  9:27 dpdklab
2024-12-10  3:31 dpdklab
2024-12-10  2:09 dpdklab
2024-12-10  2:06 dpdklab
2024-12-10  1:54 dpdklab
2024-12-10  1:50 dpdklab
2024-12-10  1:49 dpdklab
2024-12-10  1:44 dpdklab
2024-12-10  1:42 dpdklab
2024-12-10  1:40 dpdklab
2024-12-10  1:40 dpdklab
2024-12-10  1:32 dpdklab
2024-12-10  1:29 dpdklab
2024-12-10  1:23 dpdklab
2024-12-08  3:22 dpdklab
2024-12-08  2:08 dpdklab
2024-12-08  2:05 dpdklab
2024-12-08  1:49 dpdklab
2024-12-08  1:48 dpdklab
2024-12-08  1:47 dpdklab
2024-12-08  1:43 dpdklab
2024-12-08  1:40 dpdklab
2024-12-08  1:39 dpdklab
2024-12-08  1:31 dpdklab
2024-12-08  1:30 dpdklab
2024-12-08  1:23 dpdklab
2024-12-06  4:23 dpdklab
2024-12-06  2:02 dpdklab
2024-12-06  2:00 dpdklab
2024-12-06  1:59 dpdklab
2024-12-06  1:50 dpdklab
2024-12-06  1:48 dpdklab
2024-12-06  1:45 dpdklab
2024-12-06  1:43 dpdklab
2024-12-06  1:40 dpdklab
2024-12-06  1:39 dpdklab
2024-12-06  1:32 dpdklab
2024-12-06  1:31 dpdklab
2024-12-06  0:33 dpdklab
2024-12-05 22:27 dpdklab
2024-12-05 21:56 dpdklab
2024-12-05 21:44 dpdklab
2024-12-05 21:37 dpdklab
2024-12-05 21:35 dpdklab
2024-12-05 21:33 dpdklab
2024-12-05 21:30 dpdklab
2024-12-05 21:29 dpdklab
2024-12-05 21:26 dpdklab
2024-12-05 21:25 dpdklab
2024-12-05 21:17 dpdklab
2024-12-05 21:09 dpdklab
2024-12-05 21:09 dpdklab
2024-12-04 21:19 dpdklab
2024-12-04 20:05 dpdklab
2024-12-04 20:03 dpdklab
2024-12-04 19:57 dpdklab
2024-12-04 19:51 dpdklab
2024-12-04 19:42 dpdklab
2024-12-04 19:34 dpdklab
2024-12-04 19:34 dpdklab
2024-12-04 19:31 dpdklab
2024-12-04 19:30 dpdklab
2024-12-04 19:22 dpdklab
2024-12-04 19:17 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=675cafa9.050a0220.342e79.0c07SMTPIN_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).