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| pw149223-149228 [PATCH] [v2,6/6] buildtools: externally ch
Date: Sat, 14 Dec 2024 14:07:08 -0800 (PST)	[thread overview]
Message-ID: <675e018c.0d0a0220.18dbcf.91e7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241213105010.1527683-7-david.marchand@redhat.com>

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

_Testing PASS_

Submitter: David Marchand <david.marchand@redhat.com>
Date: Friday, December 13 2024 10:50:10 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:7df61db6c387703a36306c1aea92225921e2eeb2

149223-149228 --> testing pass

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

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Fedora 39           | PASS           |
+---------------------+----------------+
| Fedora 39 (Clang)   | PASS           |
+---------------------+----------------+
| Debian 12           | PASS           |
+---------------------+----------------+
| Ubuntu 20.04        | PASS           |
+---------------------+----------------+
| Fedora 40 (Clang)   | PASS           |
+---------------------+----------------+
| RHEL9               | PASS           |
+---------------------+----------------+
| Fedora 40           | PASS           |
+---------------------+----------------+
| RHEL8               | PASS           |
+---------------------+----------------+
| Ubuntu 22.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)

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

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

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

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

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)

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

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/patchsets/32135/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-12-14 22:07 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241213105010.1527683-7-david.marchand@redhat.com>
2024-12-13 10:19 ` |SUCCESS| pw149223-149228 [PATCH v2 6/6] buildtools: externally check exported headers qemudev
2024-12-13 10:24 ` qemudev
2024-12-13 10:52 ` |WARNING| pw149228 " checkpatch
2024-12-13 11:43 ` |SUCCESS| " 0-day Robot
2024-12-14 10:45 ` |SUCCESS| pw149223-149228 [PATCH] [v2,6/6] buildtools: externally ch dpdklab
2024-12-14 10:51 ` dpdklab
2024-12-14 11:17 ` dpdklab
2024-12-14 11:45 ` dpdklab
2024-12-14 12:10 ` dpdklab
2024-12-14 12:16 ` dpdklab
2024-12-14 12:31 ` dpdklab
2024-12-14 12:33 ` dpdklab
2024-12-14 12:37 ` dpdklab
2024-12-14 12:44 ` dpdklab
2024-12-14 12:45 ` dpdklab
2024-12-14 12:46 ` dpdklab
2024-12-14 13:20 ` dpdklab
2024-12-14 14:13 ` dpdklab
2024-12-14 14:25 ` |PENDING| " dpdklab
2024-12-14 14:36 ` dpdklab
2024-12-14 14:36 ` |SUCCESS| " dpdklab
2024-12-14 14:37 ` dpdklab
2024-12-14 14:37 ` dpdklab
2024-12-14 14:59 ` |WARNING| " dpdklab
2024-12-14 15:00 ` dpdklab
2024-12-14 15:00 ` dpdklab
2024-12-14 15:01 ` |PENDING| " dpdklab
2024-12-14 15:01 ` |WARNING| " dpdklab
2024-12-14 15:03 ` |SUCCESS| " dpdklab
2024-12-14 15:04 ` dpdklab
2024-12-14 15:12 ` dpdklab
2024-12-14 15:23 ` dpdklab
2024-12-14 15:44 ` dpdklab
2024-12-14 16:09 ` dpdklab
2024-12-14 16:31 ` dpdklab
2024-12-14 16:36 ` dpdklab
2024-12-14 16:40 ` |WARNING| " dpdklab
2024-12-14 16:45 ` |SUCCESS| " dpdklab
2024-12-14 17:05 ` dpdklab
2024-12-14 17:35 ` dpdklab
2024-12-14 19:37 ` dpdklab
2024-12-14 21:27 ` dpdklab
2024-12-14 22:07 ` dpdklab [this message]
2024-12-14 23:27 ` dpdklab
2024-12-14 23:54 ` 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=675e018c.0d0a0220.18dbcf.91e7SMTPIN_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).