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| pw140307 [PATCH] [v2] doc: remove empty section from testp
Date: Fri, 24 May 2024 10:14:23 -0700 (PDT)	[thread overview]
Message-ID: <6650caef.050a0220.60dc4.5fc6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240524160316.1607915-1-thomas@monjalon.net>

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

_Testing PASS_

Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: Friday, May 24 2024 16:02:09 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2dbb63594a9a985e2c8639b57f9fcd1468b9de97

140307 --> testing pass

Test environment and result as below:

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


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

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

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

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

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

Fedora 39
	Kernel: Depends on container host
	Compiler: clang 17.0.6

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

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

RHEL8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)

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

Ubuntu 20.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

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/30006/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-05-24 17:14 UTC|newest]

Thread overview: 86+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240524160316.1607915-1-thomas@monjalon.net>
2024-05-24 15:37 ` |SUCCESS| pw140307 [PATCH v2] doc: remove empty section from testpmd guide qemudev
2024-05-24 15:41 ` qemudev
2024-05-24 16:04 ` checkpatch
2024-05-24 16:46 ` |SUCCESS| pw140307 [PATCH] [v2] doc: remove empty section from testp dpdklab
2024-05-24 16:47 ` dpdklab
2024-05-24 16:54 ` dpdklab
2024-05-24 16:54 ` dpdklab
2024-05-24 17:01 ` dpdklab
2024-05-24 17:02 ` dpdklab
2024-05-24 17:02 ` dpdklab
2024-05-24 17:02 ` dpdklab
2024-05-24 17:03 ` dpdklab
2024-05-24 17:03 ` dpdklab
2024-05-24 17:03 ` dpdklab
2024-05-24 17:03 ` dpdklab
2024-05-24 17:04 ` |SUCCESS| pw140307 [PATCH v2] doc: remove empty section from testpmd guide 0-day Robot
2024-05-24 17:04 ` |SUCCESS| pw140307 [PATCH] [v2] doc: remove empty section from testp dpdklab
2024-05-24 17:04 ` dpdklab
2024-05-24 17:04 ` dpdklab
2024-05-24 17:04 ` dpdklab
2024-05-24 17:05 ` dpdklab
2024-05-24 17:05 ` dpdklab
2024-05-24 17:05 ` dpdklab
2024-05-24 17:06 ` dpdklab
2024-05-24 17:06 ` dpdklab
2024-05-24 17:07 ` dpdklab
2024-05-24 17:07 ` dpdklab
2024-05-24 17:07 ` dpdklab
2024-05-24 17:07 ` dpdklab
2024-05-24 17:08 ` dpdklab
2024-05-24 17:08 ` dpdklab
2024-05-24 17:08 ` dpdklab
2024-05-24 17:09 ` dpdklab
2024-05-24 17:09 ` dpdklab
2024-05-24 17:09 ` dpdklab
2024-05-24 17:09 ` dpdklab
2024-05-24 17:10 ` dpdklab
2024-05-24 17:10 ` dpdklab
2024-05-24 17:10 ` dpdklab
2024-05-24 17:10 ` dpdklab
2024-05-24 17:10 ` dpdklab
2024-05-24 17:10 ` dpdklab
2024-05-24 17:11 ` dpdklab
2024-05-24 17:11 ` dpdklab
2024-05-24 17:11 ` dpdklab
2024-05-24 17:11 ` dpdklab
2024-05-24 17:11 ` dpdklab
2024-05-24 17:12 ` dpdklab
2024-05-24 17:12 ` dpdklab
2024-05-24 17:12 ` dpdklab
2024-05-24 17:13 ` dpdklab
2024-05-24 17:13 ` dpdklab
2024-05-24 17:13 ` dpdklab
2024-05-24 17:13 ` dpdklab
2024-05-24 17:14 ` dpdklab
2024-05-24 17:14 ` dpdklab [this message]
2024-05-24 17:14 ` dpdklab
2024-05-24 17:14 ` dpdklab
2024-05-24 17:15 ` dpdklab
2024-05-24 17:15 ` dpdklab
2024-05-24 17:15 ` dpdklab
2024-05-24 17:15 ` dpdklab
2024-05-24 17:15 ` dpdklab
2024-05-24 17:15 ` dpdklab
2024-05-24 17:16 ` dpdklab
2024-05-24 17:17 ` dpdklab
2024-05-24 17:17 ` dpdklab
2024-05-24 17:17 ` dpdklab
2024-05-24 17:18 ` dpdklab
2024-05-24 17:18 ` dpdklab
2024-05-24 17:18 ` dpdklab
2024-05-24 17:18 ` dpdklab
2024-05-24 17:18 ` dpdklab
2024-05-24 17:40 ` dpdklab
2024-05-24 17:40 ` dpdklab
2024-05-24 17:41 ` dpdklab
2024-05-24 17:41 ` dpdklab
2024-05-24 17:41 ` dpdklab
2024-05-24 17:42 ` dpdklab
2024-05-24 17:43 ` dpdklab
2024-05-24 17:43 ` dpdklab
2024-05-24 17:44 ` dpdklab
2024-05-24 17:47 ` dpdklab
2024-05-24 17:57 ` dpdklab
2024-05-24 18:08 ` dpdklab
2024-05-24 18:10 ` 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=6650caef.050a0220.60dc4.5fc6SMTPIN_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).