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| pw139191-139198 [PATCH] [v7,8/8] doc: update documentation
Date: Tue, 09 Apr 2024 02:09:15 -0700 (PDT)	[thread overview]
Message-ID: <661505bb.050a0220.3b6f8.bbdcSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240408212438.414099-9-stephen@networkplumber.org>

Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/139198

_Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Monday, April 08 2024 21:18:39 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e2e546ab5bf5e024986ccb5310ab43982f3bb40c

139191-139198 --> testing pass

Test environment and result as below:

+---------------------+--------------------+----------------------+-------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_msvc_compile |
+=====================+====================+======================+===================+
| Windows Server 2019 | PASS               | PASS                 | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| FreeBSD 13.2        | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Windows Server 2022 | PASS               | PASS                 | PASS              |
+---------------------+--------------------+----------------------+-------------------+
| Debian Bullseye     | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| CentOS Stream 9     | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Debian 12           | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| CentOS Stream 8     | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Fedora 37           | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Fedora 38           | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Fedora 39           | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Ubuntu 22.04        | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| RHEL8               | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| openSUSE Leap 15    | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Alpine              | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Ubuntu 20.04        | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+


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

FreeBSD 13.2
	Kernel: 13.2
	Compiler: clang 14.0.5

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

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

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

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

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

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

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

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

Alpine
	Kernel: 5.4.0-167-generic
	Compiler: gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924

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

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

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-09  9:09 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240408212438.414099-9-stephen@networkplumber.org>
2024-04-08 21:12 ` |SUCCESS| pw139191-139198 [PATCH v7 8/8] doc: update documentation of TAP PMD qemudev
2024-04-08 21:16 ` qemudev
2024-04-08 21:27 ` |WARNING| pw139198 " checkpatch
2024-04-08 22:24 ` |SUCCESS| " 0-day Robot
2024-04-09  5:57 ` |SUCCESS| pw139191-139198 [PATCH] [v7,8/8] doc: update documentation dpdklab
2024-04-09  6:43 ` dpdklab
2024-04-09  6:48 ` dpdklab
2024-04-09  6:58 ` dpdklab
2024-04-09  7:00 ` dpdklab
2024-04-09  7:10 ` dpdklab
2024-04-09  7:10 ` dpdklab
2024-04-09  7:11 ` dpdklab
2024-04-09  7:12 ` dpdklab
2024-04-09  7:13 ` dpdklab
2024-04-09  7:14 ` dpdklab
2024-04-09  7:15 ` dpdklab
2024-04-09  7:15 ` dpdklab
2024-04-09  7:16 ` dpdklab
2024-04-09  7:16 ` dpdklab
2024-04-09  7:17 ` dpdklab
2024-04-09  7:20 ` dpdklab
2024-04-09  7:26 ` dpdklab
2024-04-09  7:35 ` dpdklab
2024-04-09  7:47 ` dpdklab
2024-04-09  8:15 ` dpdklab
2024-04-09  8:18 ` dpdklab
2024-04-09  8:22 ` dpdklab
2024-04-09  8:23 ` dpdklab
2024-04-09  8:25 ` dpdklab
2024-04-09  8:29 ` dpdklab
2024-04-09  8:41 ` dpdklab
2024-04-09  8:44 ` dpdklab
2024-04-09  8:45 ` dpdklab
2024-04-09  8:46 ` dpdklab
2024-04-09  8:51 ` dpdklab
2024-04-09  8:54 ` dpdklab
2024-04-09  8:59 ` dpdklab
2024-04-09  9:01 ` dpdklab
2024-04-09  9:03 ` dpdklab
2024-04-09  9:04 ` dpdklab
2024-04-09  9:05 ` dpdklab
2024-04-09  9:06 ` dpdklab
2024-04-09  9:06 ` dpdklab
2024-04-09  9:07 ` dpdklab
2024-04-09  9:07 ` dpdklab
2024-04-09  9:07 ` dpdklab
2024-04-09  9:07 ` dpdklab
2024-04-09  9:08 ` dpdklab
2024-04-09  9:08 ` dpdklab
2024-04-09  9:08 ` dpdklab
2024-04-09  9:09 ` dpdklab
2024-04-09  9:09 ` dpdklab [this message]
2024-04-09  9:09 ` dpdklab
2024-04-09  9:09 ` dpdklab
2024-04-09  9:10 ` dpdklab
2024-04-09  9:10 ` dpdklab
2024-04-09  9:10 ` dpdklab
2024-04-09  9:10 ` dpdklab
2024-04-09  9:10 ` dpdklab
2024-04-09  9:10 ` dpdklab
2024-04-09  9:11 ` dpdklab
2024-04-09  9:11 ` dpdklab
2024-04-09  9:11 ` dpdklab
2024-04-09  9:11 ` dpdklab
2024-04-09  9:12 ` dpdklab
2024-04-09  9:12 ` dpdklab
2024-04-09  9:12 ` dpdklab
2024-04-09  9:12 ` dpdklab
2024-04-09  9:12 ` dpdklab
2024-04-09  9:12 ` dpdklab
2024-04-09  9:13 ` dpdklab
2024-04-09  9:13 ` dpdklab
2024-04-09  9:13 ` dpdklab
2024-04-09  9:13 ` dpdklab
2024-04-09  9:13 ` dpdklab
2024-04-09  9:13 ` dpdklab
2024-04-09  9:13 ` dpdklab
2024-04-09  9:14 ` dpdklab
2024-04-09 10:05 ` dpdklab
2024-04-09 10:05 ` dpdklab
2024-04-09 10:21 ` dpdklab
2024-04-09 10:28 ` dpdklab
2024-04-09 10:28 ` dpdklab
2024-04-09 10:31 ` dpdklab
2024-04-09 10:35 ` dpdklab
2024-04-09 10:41 ` dpdklab
2024-04-09 10:55 ` dpdklab
2024-04-09 11:33 ` dpdklab
2024-04-09 12:11 ` dpdklab
2024-04-09 15:20 ` 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=661505bb.050a0220.3b6f8.bbdcSMTPIN_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).