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| pw142859-142865 [PATCH] [v2,7/7] devtools: add script to g
Date: Fri, 02 Aug 2024 07:35:25 -0700 (PDT)	[thread overview]
Message-ID: <66aceead.5e0a0220.f501b.2f81SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240802124411.485430-8-bruce.richardson@intel.com>

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

_Testing pending_

Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Friday, August 02 2024 12:44:11 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:b3485f4293997d35b6daecc3437bb0c183a51fb3

142859-142865 --> testing pending

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

Test environment and result as below:

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


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

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

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 39
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Fedora 38 (Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.6

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

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

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

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

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

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.4.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

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

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

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

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-02 14:35 UTC|newest]

Thread overview: 111+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240802124411.485430-8-bruce.richardson@intel.com>
2024-08-02 12:27 ` |SUCCESS| pw142859-142865 [PATCH v2 7/7] devtools: add script to generate DPDK dependency graphs qemudev
2024-08-02 12:31 ` qemudev
2024-08-02 12:46 ` |SUCCESS| pw142865 " checkpatch
2024-08-02 13:42 ` 0-day Robot
2024-08-02 13:42 ` |PENDING| pw142859-142865 [PATCH] [v2,7/7] devtools: add script to g dpdklab
2024-08-02 13:43 ` |SUCCESS| " dpdklab
2024-08-02 13:45 ` dpdklab
2024-08-02 13:46 ` |PENDING| " dpdklab
2024-08-02 13:47 ` |SUCCESS| " dpdklab
2024-08-02 13:47 ` |PENDING| " dpdklab
2024-08-02 13:47 ` |SUCCESS| " dpdklab
2024-08-02 13:48 ` dpdklab
2024-08-02 13:52 ` dpdklab
2024-08-02 13:54 ` |PENDING| " dpdklab
2024-08-02 13:54 ` dpdklab
2024-08-02 13:56 ` |FAILURE| " dpdklab
2024-08-02 13:56 ` |PENDING| " dpdklab
2024-08-02 13:56 ` |SUCCESS| " dpdklab
2024-08-02 13:56 ` |FAILURE| " dpdklab
2024-08-02 13:57 ` |SUCCESS| " dpdklab
2024-08-02 13:58 ` |PENDING| " dpdklab
2024-08-02 13:59 ` |SUCCESS| " dpdklab
2024-08-02 13:59 ` |PENDING| " dpdklab
2024-08-02 14:01 ` |SUCCESS| " dpdklab
2024-08-02 14:04 ` |PENDING| " dpdklab
2024-08-02 14:05 ` dpdklab
2024-08-02 14:06 ` dpdklab
2024-08-02 14:07 ` dpdklab
2024-08-02 14:07 ` dpdklab
2024-08-02 14:13 ` dpdklab
2024-08-02 14:13 ` dpdklab
2024-08-02 14:14 ` dpdklab
2024-08-02 14:15 ` dpdklab
2024-08-02 14:15 ` dpdklab
2024-08-02 14:16 ` dpdklab
2024-08-02 14:17 ` |SUCCESS| " dpdklab
2024-08-02 14:18 ` |PENDING| " dpdklab
2024-08-02 14:18 ` dpdklab
2024-08-02 14:19 ` dpdklab
2024-08-02 14:22 ` dpdklab
2024-08-02 14:25 ` dpdklab
2024-08-02 14:27 ` dpdklab
2024-08-02 14:28 ` dpdklab
2024-08-02 14:28 ` dpdklab
2024-08-02 14:31 ` |FAILURE| " dpdklab
2024-08-02 14:32 ` |PENDING| " dpdklab
2024-08-02 14:32 ` |SUCCESS| " dpdklab
2024-08-02 14:32 ` |PENDING| " dpdklab
2024-08-02 14:35 ` dpdklab
2024-08-02 14:35 ` dpdklab [this message]
2024-08-02 14:35 ` dpdklab
2024-08-02 14:36 ` dpdklab
2024-08-02 14:38 ` dpdklab
2024-08-02 14:39 ` dpdklab
2024-08-02 14:39 ` |SUCCESS| " dpdklab
2024-08-02 14:40 ` |PENDING| " dpdklab
2024-08-02 14:42 ` dpdklab
2024-08-02 14:42 ` dpdklab
2024-08-02 14:44 ` dpdklab
2024-08-02 14:44 ` dpdklab
2024-08-02 14:45 ` dpdklab
2024-08-02 14:45 ` dpdklab
2024-08-02 14:48 ` dpdklab
2024-08-02 14:48 ` dpdklab
2024-08-02 14:48 ` dpdklab
2024-08-02 14:49 ` dpdklab
2024-08-02 14:50 ` |FAILURE| " dpdklab
2024-08-02 14:52 ` dpdklab
2024-08-02 14:52 ` |PENDING| " dpdklab
2024-08-02 14:53 ` dpdklab
2024-08-02 14:54 ` dpdklab
2024-08-02 14:57 ` dpdklab
2024-08-02 14:59 ` dpdklab
2024-08-02 15:00 ` |FAILURE| " dpdklab
2024-08-02 15:01 ` |SUCCESS| " dpdklab
2024-08-02 15:01 ` |PENDING| " dpdklab
2024-08-02 15:01 ` dpdklab
2024-08-02 15:02 ` dpdklab
2024-08-02 15:03 ` dpdklab
2024-08-02 15:04 ` dpdklab
2024-08-02 15:05 ` |FAILURE| " dpdklab
2024-08-02 15:08 ` |SUCCESS| " dpdklab
2024-08-02 15:11 ` |FAILURE| " dpdklab
2024-08-02 15:13 ` dpdklab
2024-08-02 15:14 ` dpdklab
2024-08-02 15:14 ` dpdklab
2024-08-02 15:16 ` dpdklab
2024-08-02 15:19 ` dpdklab
2024-08-02 15:19 ` |PENDING| " dpdklab
2024-08-02 15:21 ` |FAILURE| " dpdklab
2024-08-02 15:23 ` dpdklab
2024-08-02 15:28 ` |PENDING| " dpdklab
2024-08-02 15:28 ` |FAILURE| " dpdklab
2024-08-02 15:29 ` dpdklab
2024-08-02 15:34 ` dpdklab
2024-08-02 15:34 ` |PENDING| " dpdklab
2024-08-02 15:43 ` dpdklab
2024-08-02 15:46 ` |FAILURE| " dpdklab
2024-08-02 15:50 ` |PENDING| " dpdklab
2024-08-02 15:54 ` dpdklab
2024-08-02 15:56 ` dpdklab
2024-08-02 16:01 ` dpdklab
2024-08-02 16:01 ` dpdklab
2024-08-02 16:04 ` dpdklab
2024-08-02 16:15 ` dpdklab
2024-08-02 16:22 ` dpdklab
2024-08-02 16:26 ` |SUCCESS| " dpdklab
2024-08-03  9:12 ` dpdklab
2024-08-06 11:59 ` dpdklab
2024-08-06 12:08 ` dpdklab
2024-08-06 12:24 ` 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=66aceead.5e0a0220.f501b.2f81SMTPIN_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).