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: |PENDING| pw142883-142893 [PATCH] [v4,11/11] doc: update nfp documen
Date: Sun, 04 Aug 2024 21:02:49 -0700 (PDT)	[thread overview]
Message-ID: <66b04ee9.050a0220.5903f.59e0SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240805021248.1051198-12-chaoyong.he@corigine.com>

Test-Label: iol-unit-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/142893

_Testing pending_

Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Monday, August 05 2024 02:12:48 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:37ce4c84c0f23c3989bc7ae19e03a4593cec94e5

142883-142893 --> testing pending

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

Test environment and result as below:

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


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

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

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

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

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 38 (Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.6

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

Fedora 39 (Clang)
	Kernel: Depends on container host
	Compiler: clang 17.0.6

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

Fedora 40 (Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.6

Fedora 40
	Kernel: Depends on container host
	Compiler: gcc 14.1.1

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

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1

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

Ubuntu 24.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 13.2.0

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-08-05  4:02 UTC|newest]

Thread overview: 110+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240805021248.1051198-12-chaoyong.he@corigine.com>
2024-08-05  1:48 ` |SUCCESS| pw142883-142893 [PATCH v4 11/11] doc: update nfp document qemudev
2024-08-05  1:52 ` qemudev
2024-08-05  2:16 ` |SUCCESS| pw142893 " checkpatch
2024-08-05  2:50 ` |SUCCESS| pw142883-142893 [PATCH] [v4,11/11] doc: update nfp documen dpdklab
2024-08-05  2:54 ` dpdklab
2024-08-05  2:55 ` dpdklab
2024-08-05  2:55 ` |PENDING| " dpdklab
2024-08-05  2:55 ` |SUCCESS| " dpdklab
2024-08-05  2:56 ` |PENDING| " dpdklab
2024-08-05  2:56 ` dpdklab
2024-08-05  2:57 ` dpdklab
2024-08-05  2:58 ` dpdklab
2024-08-05  2:59 ` |SUCCESS| " dpdklab
2024-08-05  3:00 ` |PENDING| " dpdklab
2024-08-05  3:00 ` dpdklab
2024-08-05  3:01 ` dpdklab
2024-08-05  3:01 ` |SUCCESS| " dpdklab
2024-08-05  3:02 ` |SUCCESS| pw142893 [PATCH v4 11/11] doc: update nfp document 0-day Robot
2024-08-05  3:03 ` |PENDING| pw142883-142893 [PATCH] [v4,11/11] doc: update nfp documen dpdklab
2024-08-05  3:03 ` |SUCCESS| " dpdklab
2024-08-05  3:03 ` |PENDING| " dpdklab
2024-08-05  3:04 ` dpdklab
2024-08-05  3:04 ` dpdklab
2024-08-05  3:05 ` dpdklab
2024-08-05  3:06 ` dpdklab
2024-08-05  3:07 ` dpdklab
2024-08-05  3:07 ` dpdklab
2024-08-05  3:07 ` dpdklab
2024-08-05  3:08 ` dpdklab
2024-08-05  3:08 ` dpdklab
2024-08-05  3:09 ` dpdklab
2024-08-05  3:10 ` dpdklab
2024-08-05  3:11 ` dpdklab
2024-08-05  3:11 ` dpdklab
2024-08-05  3:11 ` dpdklab
2024-08-05  3:11 ` dpdklab
2024-08-05  3:11 ` |SUCCESS| " dpdklab
2024-08-05  3:11 ` |PENDING| " dpdklab
2024-08-05  3:11 ` dpdklab
2024-08-05  3:11 ` dpdklab
2024-08-05  3:12 ` dpdklab
2024-08-05  3:12 ` dpdklab
2024-08-05  3:13 ` |SUCCESS| " dpdklab
2024-08-05  3:16 ` |PENDING| " dpdklab
2024-08-05  3:16 ` dpdklab
2024-08-05  3:16 ` dpdklab
2024-08-05  3:17 ` |SUCCESS| " dpdklab
2024-08-05  3:19 ` |PENDING| " dpdklab
2024-08-05  3:20 ` dpdklab
2024-08-05  3:21 ` dpdklab
2024-08-05  3:22 ` dpdklab
2024-08-05  3:22 ` dpdklab
2024-08-05  3:23 ` dpdklab
2024-08-05  3:23 ` dpdklab
2024-08-05  3:24 ` dpdklab
2024-08-05  3:24 ` dpdklab
2024-08-05  3:24 ` dpdklab
2024-08-05  3:27 ` dpdklab
2024-08-05  3:27 ` dpdklab
2024-08-05  3:28 ` dpdklab
2024-08-05  3:28 ` dpdklab
2024-08-05  3:34 ` dpdklab
2024-08-05  3:35 ` dpdklab
2024-08-05  3:36 ` dpdklab
2024-08-05  3:36 ` dpdklab
2024-08-05  3:37 ` dpdklab
2024-08-05  3:38 ` dpdklab
2024-08-05  3:39 ` dpdklab
2024-08-05  3:40 ` dpdklab
2024-08-05  3:41 ` dpdklab
2024-08-05  3:41 ` dpdklab
2024-08-05  3:42 ` dpdklab
2024-08-05  3:43 ` dpdklab
2024-08-05  3:43 ` |SUCCESS| " dpdklab
2024-08-05  3:45 ` |PENDING| " dpdklab
2024-08-05  3:46 ` dpdklab
2024-08-05  3:47 ` |SUCCESS| " dpdklab
2024-08-05  3:47 ` |PENDING| " dpdklab
2024-08-05  3:48 ` dpdklab
2024-08-05  3:49 ` dpdklab
2024-08-05  3:49 ` dpdklab
2024-08-05  3:50 ` dpdklab
2024-08-05  3:50 ` dpdklab
2024-08-05  3:51 ` dpdklab
2024-08-05  3:51 ` dpdklab
2024-08-05  3:52 ` dpdklab
2024-08-05  3:54 ` dpdklab
2024-08-05  3:57 ` dpdklab
2024-08-05  3:57 ` dpdklab
2024-08-05  3:58 ` |SUCCESS| " dpdklab
2024-08-05  3:59 ` |PENDING| " dpdklab
2024-08-05  4:02 ` dpdklab [this message]
2024-08-05  4:03 ` dpdklab
2024-08-05  4:04 ` |SUCCESS| " dpdklab
2024-08-05  4:06 ` dpdklab
2024-08-05  4:06 ` |PENDING| " dpdklab
2024-08-05  4:07 ` dpdklab
2024-08-05  4:10 ` dpdklab
2024-08-05  4:10 ` dpdklab
2024-08-05  4:11 ` dpdklab
2024-08-05  4:14 ` dpdklab
2024-08-05  4:15 ` dpdklab
2024-08-05  4:15 ` dpdklab
2024-08-05  4:18 ` dpdklab
2024-08-05  4:28 ` dpdklab
2024-08-05  4:33 ` |SUCCESS| " dpdklab
2024-08-05  4:42 ` dpdklab
2024-08-06 18:41 ` dpdklab
2024-08-06 18:50 ` dpdklab
2024-08-06 19:06 ` 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=66b04ee9.050a0220.5903f.59e0SMTPIN_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).