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| pw143746-143749 [PATCH] [v2,4/4] devtools/test-meson-build
Date: Wed, 11 Sep 2024 00:20:30 -0700 (PDT)	[thread overview]
Message-ID: <66e144be.050a0220.1fd5d8.ef0fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240906161244.1663967-5-bruce.richardson@intel.com>

Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/143749

_Testing PASS_

Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Friday, September 06 2024 16:12:44 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43

143746-143749 --> testing pass

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

Test environment and result as below:

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


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

Debian Bullseye
	Kernel: Depends on container host
	Compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1 20230508 (Red Hat 12.3.1-1)

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

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.2.1 20240316 (Red Hat 13.2.1-7)

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

Fedora 38 (Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.6 (Fedora 16.0.6-4.fc38)

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

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

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

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

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

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

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

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

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30944/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-09-11  7:20 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240906161244.1663967-5-bruce.richardson@intel.com>
2024-09-06 15:45 ` |SUCCESS| pw143746-143749 [PATCH v2 4/4] devtools/test-meson-builds: use cross files for 32bit build qemudev
2024-09-06 15:50 ` qemudev
2024-09-06 16:15 ` |WARNING| pw143749 " checkpatch
2024-09-06 17:05 ` |SUCCESS| " 0-day Robot
2024-09-11  0:33 ` |SUCCESS| pw143746-143749 [PATCH] [v2,4/4] devtools/test-meson-build dpdklab
2024-09-11  1:03 ` dpdklab
2024-09-11  2:42 ` dpdklab
2024-09-11  4:50 ` |PENDING| " dpdklab
2024-09-11  5:29 ` |SUCCESS| " dpdklab
2024-09-11  5:30 ` dpdklab
2024-09-11  5:31 ` |PENDING| " dpdklab
2024-09-11  7:20 ` dpdklab [this message]
2024-09-11  7:21 ` |SUCCESS| " dpdklab
2024-09-11  7:26 ` dpdklab
2024-09-11  7:33 ` dpdklab
2024-09-11 10:04 ` |PENDING| " dpdklab
2024-09-11 10:42 ` |SUCCESS| " dpdklab
2024-09-11 11:42 ` dpdklab
2024-09-11 12:54 ` dpdklab
2024-09-11 13:23 ` dpdklab
2024-09-11 13:52 ` dpdklab
2024-09-11 14:12 ` dpdklab
2024-09-11 14:29 ` dpdklab
2024-09-11 15:26 ` dpdklab
2024-09-11 15:31 ` dpdklab
2024-09-11 17:58 ` dpdklab
2024-09-15 20:53 ` dpdklab
2024-09-16  2:21 ` 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=66e144be.050a0220.1fd5d8.ef0fSMTPIN_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).