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| pw142780 [PATCH] [v1,1/1] mldev: introduce data type conve
Date: Wed, 31 Jul 2024 13:32:15 -0700 (PDT)	[thread overview]
Message-ID: <66aa9f4f.050a0220.25a519.f179SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240731063250.9008-1-syalavarthi@marvell.com>

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

_Testing pending_

Submitter: Srikanth Yalavarthi <syalavarthi@marvell.com>
Date: Wednesday, July 31 2024 06:32:49 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:1d245ca8239d947258b3ae7cc4d8df97ef527852

142780 --> testing pending

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

Test environment and result as below:

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


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

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

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

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

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1

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

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

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)

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-07-31 20:32 UTC|newest]

Thread overview: 117+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240731063250.9008-1-syalavarthi@marvell.com>
2024-07-31  6:18 ` |SUCCESS| pw142780 [PATCH v1 1/1] mldev: introduce data type conversion functions qemudev
2024-07-31  6:23 ` qemudev
2024-07-31  6:44 ` checkpatch
2024-07-31  7:42 ` 0-day Robot
2024-07-31 12:32 ` |SUCCESS| pw142780 [PATCH] [v1,1/1] mldev: introduce data type conve dpdklab
2024-07-31 13:12 ` |PENDING| " dpdklab
2024-07-31 13:25 ` |SUCCESS| " dpdklab
2024-07-31 13:36 ` |PENDING| " dpdklab
2024-07-31 13:43 ` |SUCCESS| " dpdklab
2024-07-31 13:49 ` dpdklab
2024-07-31 13:50 ` dpdklab
2024-07-31 14:05 ` dpdklab
2024-07-31 14:18 ` |PENDING| " dpdklab
2024-07-31 14:30 ` dpdklab
2024-07-31 14:32 ` dpdklab
2024-07-31 14:35 ` dpdklab
2024-07-31 14:35 ` |SUCCESS| " dpdklab
2024-07-31 14:35 ` |PENDING| " dpdklab
2024-07-31 14:38 ` dpdklab
2024-07-31 14:43 ` dpdklab
2024-07-31 14:43 ` dpdklab
2024-07-31 14:47 ` dpdklab
2024-07-31 14:47 ` dpdklab
2024-07-31 14:48 ` dpdklab
2024-07-31 14:50 ` dpdklab
2024-07-31 15:00 ` dpdklab
2024-07-31 15:06 ` dpdklab
2024-07-31 15:08 ` dpdklab
2024-07-31 15:13 ` |SUCCESS| " dpdklab
2024-07-31 16:26 ` |PENDING| " dpdklab
2024-07-31 16:30 ` dpdklab
2024-07-31 16:32 ` dpdklab
2024-07-31 16:34 ` |SUCCESS| " dpdklab
2024-07-31 16:35 ` |PENDING| " dpdklab
2024-07-31 16:38 ` dpdklab
2024-07-31 16:49 ` dpdklab
2024-07-31 16:55 ` |SUCCESS| " dpdklab
2024-07-31 17:19 ` |PENDING| " dpdklab
2024-07-31 17:42 ` dpdklab
2024-07-31 17:55 ` dpdklab
2024-07-31 17:59 ` dpdklab
2024-07-31 18:01 ` dpdklab
2024-07-31 18:02 ` dpdklab
2024-07-31 18:03 ` |SUCCESS| " dpdklab
2024-07-31 18:06 ` |PENDING| " dpdklab
2024-07-31 18:09 ` dpdklab
2024-07-31 18:11 ` dpdklab
2024-07-31 18:15 ` dpdklab
2024-07-31 18:23 ` dpdklab
2024-07-31 18:26 ` dpdklab
2024-07-31 18:30 ` dpdklab
2024-07-31 18:35 ` dpdklab
2024-07-31 18:36 ` dpdklab
2024-07-31 18:37 ` dpdklab
2024-07-31 18:38 ` dpdklab
2024-07-31 18:38 ` dpdklab
2024-07-31 18:39 ` dpdklab
2024-07-31 18:40 ` dpdklab
2024-07-31 18:42 ` dpdklab
2024-07-31 18:47 ` dpdklab
2024-07-31 18:48 ` dpdklab
2024-07-31 18:50 ` dpdklab
2024-07-31 18:51 ` dpdklab
2024-07-31 18:52 ` dpdklab
2024-07-31 18:54 ` dpdklab
2024-07-31 18:54 ` dpdklab
2024-07-31 18:57 ` dpdklab
2024-07-31 18:59 ` dpdklab
2024-07-31 18:59 ` dpdklab
2024-07-31 18:59 ` dpdklab
2024-07-31 19:18 ` |SUCCESS| " dpdklab
2024-07-31 19:23 ` dpdklab
2024-07-31 19:27 ` dpdklab
2024-07-31 19:32 ` dpdklab
2024-07-31 19:53 ` dpdklab
2024-07-31 20:02 ` |PENDING| " dpdklab
2024-07-31 20:11 ` dpdklab
2024-07-31 20:12 ` dpdklab
2024-07-31 20:14 ` dpdklab
2024-07-31 20:18 ` dpdklab
2024-07-31 20:19 ` dpdklab
2024-07-31 20:19 ` dpdklab
2024-07-31 20:24 ` dpdklab
2024-07-31 20:26 ` dpdklab
2024-07-31 20:31 ` dpdklab
2024-07-31 20:31 ` dpdklab
2024-07-31 20:32 ` dpdklab [this message]
2024-07-31 20:36 ` dpdklab
2024-07-31 20:37 ` dpdklab
2024-07-31 20:37 ` dpdklab
2024-07-31 20:42 ` dpdklab
2024-07-31 20:42 ` dpdklab
2024-07-31 20:48 ` |SUCCESS| " dpdklab
2024-07-31 20:48 ` |PENDING| " dpdklab
2024-07-31 20:51 ` |SUCCESS| " dpdklab
2024-07-31 21:16 ` |PENDING| " dpdklab
2024-07-31 21:18 ` dpdklab
2024-07-31 21:22 ` dpdklab
2024-07-31 21:24 ` dpdklab
2024-07-31 21:25 ` dpdklab
2024-07-31 21:25 ` dpdklab
2024-07-31 21:26 ` dpdklab
2024-07-31 21:28 ` dpdklab
2024-07-31 21:30 ` dpdklab
2024-07-31 21:30 ` dpdklab
2024-07-31 21:31 ` dpdklab
2024-07-31 21:33 ` dpdklab
2024-07-31 21:34 ` dpdklab
2024-07-31 21:35 ` dpdklab
2024-07-31 21:36 ` dpdklab
2024-07-31 21:37 ` dpdklab
2024-07-31 21:38 ` dpdklab
2024-07-31 21:41 ` dpdklab
2024-07-31 21:46 ` dpdklab
2024-07-31 21:48 ` |SUCCESS| " dpdklab
2024-07-31 22:05 ` dpdklab
2024-08-01 18:49 ` 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=66aa9f4f.050a0220.25a519.f179SMTPIN_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).