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| pw139757 [PATCH] maintainers: update for eal
Date: Tue, 30 Apr 2024 15:26:18 -0700 (PDT)	[thread overview]
Message-ID: <6631700a.b00a0220.d57ca.71d2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1714510339-10416-1-git-send-email-roretzla@linux.microsoft.com>

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

_Testing PASS_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Tuesday, April 30 2024 20:52:19 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:7e06c0de1952d3109a5b0c4779d7e7d8059c9d78

139757 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Debian 12           | PASS           |
+---------------------+----------------+
| Fedora 38           | PASS           |
+---------------------+----------------+
| Fedora 39           | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| Fedora 37           | PASS           |
+---------------------+----------------+
| RHEL8               | PASS           |
+---------------------+----------------+
| Ubuntu 20.04        | PASS           |
+---------------------+----------------+
| openSUSE Leap 15    | PASS           |
+---------------------+----------------+
| Windows Server 2022 | PASS           |
+---------------------+----------------+
| Ubuntu 22.04        | PASS           |
+---------------------+----------------+


Windows Server 2019
	Kernel: 10.0.17763
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

Debian Bullseye
	Kernel: 5.4.0-167-generic
	Compiler: gcc 10.2.1-6

CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Fedora 39
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

CentOS Stream 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

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

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

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

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

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-04-30 22:26 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1714510339-10416-1-git-send-email-roretzla@linux.microsoft.com>
2024-04-30 20:25 ` qemudev
2024-04-30 20:30 ` qemudev
2024-04-30 21:39 ` dpdklab
2024-04-30 21:39 ` dpdklab
2024-04-30 21:40 ` dpdklab
2024-04-30 21:40 ` dpdklab
2024-04-30 21:41 ` dpdklab
2024-04-30 21:41 ` dpdklab
2024-04-30 21:42 ` dpdklab
2024-04-30 21:43 ` 0-day Robot
2024-04-30 21:46 ` dpdklab
2024-04-30 21:47 ` dpdklab
2024-04-30 21:47 ` dpdklab
2024-04-30 21:47 ` dpdklab
2024-04-30 21:48 ` dpdklab
2024-04-30 21:48 ` dpdklab
2024-04-30 21:48 ` dpdklab
2024-04-30 21:48 ` dpdklab
2024-04-30 21:48 ` dpdklab
2024-04-30 21:48 ` dpdklab
2024-04-30 21:49 ` dpdklab
2024-04-30 21:49 ` dpdklab
2024-04-30 21:49 ` dpdklab
2024-04-30 21:49 ` dpdklab
2024-04-30 21:50 ` dpdklab
2024-04-30 21:50 ` dpdklab
2024-04-30 21:50 ` dpdklab
2024-04-30 21:50 ` dpdklab
2024-04-30 21:50 ` dpdklab
2024-04-30 21:50 ` dpdklab
2024-04-30 21:51 ` dpdklab
2024-04-30 21:51 ` dpdklab
2024-04-30 21:51 ` dpdklab
2024-04-30 21:51 ` dpdklab
2024-04-30 21:52 ` dpdklab
2024-04-30 21:54 ` dpdklab
2024-04-30 21:54 ` dpdklab
2024-04-30 21:54 ` dpdklab
2024-04-30 21:55 ` dpdklab
2024-04-30 21:55 ` dpdklab
2024-04-30 21:55 ` dpdklab
2024-04-30 21:56 ` dpdklab
2024-04-30 21:56 ` dpdklab
2024-04-30 21:56 ` dpdklab
2024-04-30 21:56 ` dpdklab
2024-04-30 21:57 ` dpdklab
2024-04-30 21:57 ` dpdklab
2024-04-30 21:57 ` dpdklab
2024-04-30 21:58 ` dpdklab
2024-04-30 21:58 ` dpdklab
2024-04-30 21:58 ` dpdklab
2024-04-30 21:58 ` dpdklab
2024-04-30 21:59 ` dpdklab
2024-04-30 22:00 ` dpdklab
2024-04-30 22:01 ` dpdklab
2024-04-30 22:01 ` dpdklab
2024-04-30 22:01 ` dpdklab
2024-04-30 22:02 ` dpdklab
2024-04-30 22:02 ` dpdklab
2024-04-30 22:06 ` dpdklab
2024-04-30 22:06 ` dpdklab
2024-04-30 22:06 ` dpdklab
2024-04-30 22:07 ` dpdklab
2024-04-30 22:07 ` dpdklab
2024-04-30 22:20 ` dpdklab
2024-04-30 22:23 ` dpdklab
2024-04-30 22:23 ` dpdklab
2024-04-30 22:24 ` dpdklab
2024-04-30 22:24 ` dpdklab
2024-04-30 22:24 ` dpdklab
2024-04-30 22:25 ` dpdklab
2024-04-30 22:26 ` dpdklab [this message]
2024-04-30 22:26 ` dpdklab
2024-04-30 22:28 ` dpdklab
2024-04-30 22:28 ` dpdklab
2024-04-30 22:31 ` dpdklab
2024-04-30 22:32 ` dpdklab
2024-04-30 22:33 ` dpdklab
2024-04-30 22:35 ` dpdklab
2024-04-30 22:36 ` dpdklab
2024-04-30 23:06 ` dpdklab
2024-04-30 23:06 ` dpdklab
2024-04-30 23:12 ` dpdklab
2024-05-01 21:38 ` dpdklab
2024-05-02 20:06 ` dpdklab
2024-05-03 15:16 ` dpdklab
2024-05-03 20:33 ` dpdklab
2024-05-05  8:12 ` dpdklab
2024-05-05  8:17 ` dpdklab
2024-05-05  8: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=6631700a.b00a0220.d57ca.71d2SMTPIN_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).