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| pw142775 [PATCH] [v1,1/1] ml/cnxk: fix incorrect handling
Date: Wed, 31 Jul 2024 15:23:20 -0700 (PDT)	[thread overview]
Message-ID: <66aab958.170a0220.343ecc.720bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240731054104.7576-1-syalavarthi@marvell.com>

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

_Testing pending_

Submitter: Srikanth Yalavarthi <syalavarthi@marvell.com>
Date: Wednesday, July 31 2024 05:41:03 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:781d698ae2acb9bc7eed06f447cb8355673f7d81

142775 --> testing pending

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

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| Windows Server 2022 | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| Debian 12           | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Fedora 37           | PASS           |
+---------------------+----------------+
| Fedora 38           | PASS           |
+---------------------+----------------+
| Fedora 38 (Clang)   | PASS           |
+---------------------+----------------+
| Fedora 39           | PEND           |
+---------------------+----------------+
| Fedora 39 (Clang)   | PEND           |
+---------------------+----------------+
| Fedora 40 (Clang)   | PEND           |
+---------------------+----------------+
| Fedora 40           | PEND           |
+---------------------+----------------+
| openSUSE Leap 15    | PEND           |
+---------------------+----------------+
| RHEL8               | PEND           |
+---------------------+----------------+
| RHEL9               | 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 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

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

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

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

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

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

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 22:23 UTC|newest]

Thread overview: 115+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240731054104.7576-1-syalavarthi@marvell.com>
2024-07-31  5:30 ` |SUCCESS| pw142775 [PATCH v1 1/1] ml/cnxk: fix incorrect handling of TVM model I/O qemudev
2024-07-31  5:35 ` qemudev
2024-07-31  5:58 ` checkpatch
2024-07-31  6:42 ` 0-day Robot
2024-07-31 12:57 ` |SUCCESS| pw142775 [PATCH] [v1,1/1] ml/cnxk: fix incorrect handling dpdklab
2024-07-31 13:41 ` |PENDING| " dpdklab
2024-07-31 13:54 ` |SUCCESS| " dpdklab
2024-07-31 14:08 ` |PENDING| " dpdklab
2024-07-31 14:14 ` |SUCCESS| " dpdklab
2024-07-31 14:20 ` dpdklab
2024-07-31 14:22 ` dpdklab
2024-07-31 14:36 ` dpdklab
2024-07-31 15:11 ` dpdklab
2024-07-31 15:21 ` |PENDING| " dpdklab
2024-07-31 15:27 ` dpdklab
2024-07-31 15:36 ` dpdklab
2024-07-31 15:37 ` dpdklab
2024-07-31 15:45 ` dpdklab
2024-07-31 15:50 ` dpdklab
2024-07-31 15:53 ` dpdklab
2024-07-31 15:54 ` dpdklab
2024-07-31 15:56 ` dpdklab
2024-07-31 16:00 ` dpdklab
2024-07-31 16:05 ` dpdklab
2024-07-31 16:20 ` dpdklab
2024-07-31 16:21 ` dpdklab
2024-07-31 16:31 ` dpdklab
2024-07-31 16:39 ` |SUCCESS| " dpdklab
2024-07-31 16:45 ` |PENDING| " dpdklab
2024-07-31 16:47 ` dpdklab
2024-07-31 16:51 ` dpdklab
2024-07-31 16:53 ` |SUCCESS| " dpdklab
2024-07-31 16:54 ` |PENDING| " dpdklab
2024-07-31 17:10 ` dpdklab
2024-07-31 17:11 ` dpdklab
2024-07-31 17:28 ` |SUCCESS| " dpdklab
2024-07-31 18:39 ` |PENDING| " dpdklab
2024-07-31 18:43 ` dpdklab
2024-07-31 18:55 ` dpdklab
2024-07-31 18:58 ` dpdklab
2024-07-31 19:00 ` dpdklab
2024-07-31 19:01 ` dpdklab
2024-07-31 19:05 ` dpdklab
2024-07-31 19:07 ` dpdklab
2024-07-31 19:08 ` dpdklab
2024-07-31 19:08 ` dpdklab
2024-07-31 19:09 ` dpdklab
2024-07-31 19:11 ` dpdklab
2024-07-31 19:12 ` dpdklab
2024-07-31 19:12 ` dpdklab
2024-07-31 19:14 ` dpdklab
2024-07-31 19:15 ` dpdklab
2024-07-31 19:17 ` dpdklab
2024-07-31 19:18 ` dpdklab
2024-07-31 19:18 ` dpdklab
2024-07-31 19:19 ` dpdklab
2024-07-31 19:21 ` dpdklab
2024-07-31 19:27 ` dpdklab
2024-07-31 19:35 ` dpdklab
2024-07-31 19:42 ` dpdklab
2024-07-31 19:45 ` dpdklab
2024-07-31 19:49 ` dpdklab
2024-07-31 19:50 ` dpdklab
2024-07-31 19:51 ` dpdklab
2024-07-31 19:54 ` dpdklab
2024-07-31 19:57 ` dpdklab
2024-07-31 20:12 ` dpdklab
2024-07-31 20:25 ` |SUCCESS| " dpdklab
2024-07-31 20:27 ` |PENDING| " dpdklab
2024-07-31 20:28 ` dpdklab
2024-07-31 20:30 ` |SUCCESS| " dpdklab
2024-07-31 20:47 ` |PENDING| " dpdklab
2024-07-31 20:59 ` |SUCCESS| " dpdklab
2024-07-31 21:09 ` |PENDING| " dpdklab
2024-07-31 21:29 ` |SUCCESS| " dpdklab
2024-07-31 21:45 ` |PENDING| " dpdklab
2024-07-31 21:45 ` dpdklab
2024-07-31 21:47 ` dpdklab
2024-07-31 21:50 ` dpdklab
2024-07-31 21:51 ` dpdklab
2024-07-31 21:52 ` dpdklab
2024-07-31 21:53 ` dpdklab
2024-07-31 21:54 ` dpdklab
2024-07-31 21:57 ` dpdklab
2024-07-31 21:58 ` dpdklab
2024-07-31 21:58 ` dpdklab
2024-07-31 22:00 ` dpdklab
2024-07-31 22:01 ` dpdklab
2024-07-31 22:01 ` dpdklab
2024-07-31 22:02 ` dpdklab
2024-07-31 22:03 ` dpdklab
2024-07-31 22:03 ` dpdklab
2024-07-31 22:05 ` |SUCCESS| " dpdklab
2024-07-31 22:06 ` |PENDING| " dpdklab
2024-07-31 22:06 ` |SUCCESS| " dpdklab
2024-07-31 22:07 ` |PENDING| " dpdklab
2024-07-31 22:14 ` dpdklab
2024-07-31 22:14 ` dpdklab
2024-07-31 22:15 ` |SUCCESS| " dpdklab
2024-07-31 22:19 ` |PENDING| " dpdklab
2024-07-31 22:22 ` dpdklab
2024-07-31 22:23 ` dpdklab
2024-07-31 22:23 ` dpdklab [this message]
2024-07-31 22:25 ` dpdklab
2024-07-31 22:26 ` dpdklab
2024-07-31 22:28 ` dpdklab
2024-07-31 22:30 ` dpdklab
2024-07-31 22:31 ` dpdklab
2024-07-31 22:31 ` dpdklab
2024-07-31 22:32 ` dpdklab
2024-07-31 22:34 ` dpdklab
2024-07-31 22:35 ` dpdklab
2024-07-31 22:37 ` |SUCCESS| " dpdklab
2024-07-31 23:04 ` |PENDING| " dpdklab
2024-08-01 20:18 ` |SUCCESS| " 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=66aab958.170a0220.343ecc.720bSMTPIN_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).