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| pw142323 [PATCH] [v2] net/virtio_user: fix issue with conv
Date: Thu, 11 Jul 2024 12:25:35 -0700 (PDT)	[thread overview]
Message-ID: <669031af.050a0220.31dba.3c96SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240711124436.2383232-1-schalla@marvell.com>

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

_Testing pending_

Submitter: Srujana Challa <schalla@marvell.com>
Date: Thursday, July 11 2024 12:44:36 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:9cbdb606e5d04de04be3d9f70f0e76551e8c9a36

142323 --> testing pending

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2022 | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| Debian 12           | PASS           |
+---------------------+----------------+
| Fedora 37           | PASS           |
+---------------------+----------------+
| Fedora 38           | PASS           |
+---------------------+----------------+
| Fedora 38 (Clang)   | PASS           |
+---------------------+----------------+
| Fedora 39           | PASS           |
+---------------------+----------------+
| Fedora 39 (Clang)   | PEND           |
+---------------------+----------------+
| Fedora 40           | PEND           |
+---------------------+----------------+
| Fedora 40 (Clang)   | PEND           |
+---------------------+----------------+
| RHEL9               | PEND           |
+---------------------+----------------+
| RHEL8               | PEND           |
+---------------------+----------------+
| openSUSE Leap 15    | PEND           |
+---------------------+----------------+
| Ubuntu 24.04        | PEND           |
+---------------------+----------------+
| Ubuntu 22.04        | PEND           |
+---------------------+----------------+
| Ubuntu 20.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

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

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

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

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

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

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)

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

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

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

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-11 19:25 UTC|newest]

Thread overview: 120+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240711124436.2383232-1-schalla@marvell.com>
2024-07-11 12:18 ` |SUCCESS| pw142323 [PATCH v2] net/virtio_user: fix issue with converting cq descriptor IOVA address to VA qemudev
2024-07-11 12:22 ` qemudev
2024-07-11 12:45 ` |WARNING| " checkpatch
2024-07-11 13:43 ` |SUCCESS| " 0-day Robot
2024-07-11 15:48 ` |SUCCESS| pw142323 [PATCH] [v2] net/virtio_user: fix issue with conv dpdklab
2024-07-11 15:51 ` dpdklab
2024-07-11 15:53 ` dpdklab
2024-07-11 15:54 ` dpdklab
2024-07-11 15:58 ` dpdklab
2024-07-11 15:59 ` dpdklab
2024-07-11 16:03 ` dpdklab
2024-07-11 16:07 ` dpdklab
2024-07-11 16:12 ` dpdklab
2024-07-11 16:16 ` dpdklab
2024-07-11 16:16 ` dpdklab
2024-07-11 16:23 ` dpdklab
2024-07-11 16:24 ` dpdklab
2024-07-11 16:27 ` dpdklab
2024-07-11 16:46 ` dpdklab
2024-07-11 16:58 ` dpdklab
2024-07-11 17:05 ` |PENDING| " dpdklab
2024-07-11 17:07 ` dpdklab
2024-07-11 17:10 ` dpdklab
2024-07-11 17:12 ` |SUCCESS| " dpdklab
2024-07-11 17:18 ` |PENDING| " dpdklab
2024-07-11 17:20 ` dpdklab
2024-07-11 17:21 ` dpdklab
2024-07-11 17:21 ` dpdklab
2024-07-11 17:27 ` dpdklab
2024-07-11 17:29 ` dpdklab
2024-07-11 17:33 ` dpdklab
2024-07-11 17:39 ` dpdklab
2024-07-11 17:40 ` dpdklab
2024-07-11 17:40 ` dpdklab
2024-07-11 17:42 ` dpdklab
2024-07-11 17:45 ` dpdklab
2024-07-11 17:45 ` dpdklab
2024-07-11 17:47 ` dpdklab
2024-07-11 17:47 ` dpdklab
2024-07-11 17:51 ` dpdklab
2024-07-11 17:52 ` dpdklab
2024-07-11 17:52 ` dpdklab
2024-07-11 17:53 ` dpdklab
2024-07-11 17:53 ` dpdklab
2024-07-11 17:53 ` dpdklab
2024-07-11 17:53 ` dpdklab
2024-07-11 17:56 ` dpdklab
2024-07-11 17:58 ` dpdklab
2024-07-11 17:59 ` dpdklab
2024-07-11 17:59 ` dpdklab
2024-07-11 18:01 ` dpdklab
2024-07-11 18:01 ` dpdklab
2024-07-11 18:02 ` dpdklab
2024-07-11 18:02 ` dpdklab
2024-07-11 18:04 ` dpdklab
2024-07-11 18:06 ` dpdklab
2024-07-11 18:06 ` dpdklab
2024-07-11 18:08 ` dpdklab
2024-07-11 18:09 ` |SUCCESS| " dpdklab
2024-07-11 18:12 ` |PENDING| " dpdklab
2024-07-11 18:16 ` dpdklab
2024-07-11 18:18 ` dpdklab
2024-07-11 18:23 ` dpdklab
2024-07-11 18:30 ` dpdklab
2024-07-11 18:31 ` dpdklab
2024-07-11 18:37 ` dpdklab
2024-07-11 18:37 ` dpdklab
2024-07-11 18:38 ` dpdklab
2024-07-11 18:39 ` dpdklab
2024-07-11 18:54 ` dpdklab
2024-07-11 18:56 ` dpdklab
2024-07-11 18:56 ` dpdklab
2024-07-11 18:59 ` dpdklab
2024-07-11 19:01 ` dpdklab
2024-07-11 19:01 ` dpdklab
2024-07-11 19:04 ` dpdklab
2024-07-11 19:09 ` dpdklab
2024-07-11 19:11 ` dpdklab
2024-07-11 19:14 ` dpdklab
2024-07-11 19:16 ` dpdklab
2024-07-11 19:25 ` dpdklab [this message]
2024-07-11 19:26 ` dpdklab
2024-07-11 19:26 ` dpdklab
2024-07-11 19:27 ` dpdklab
2024-07-11 19:29 ` dpdklab
2024-07-11 19:29 ` dpdklab
2024-07-11 19:30 ` dpdklab
2024-07-11 19:30 ` dpdklab
2024-07-11 19:36 ` dpdklab
2024-07-11 19:37 ` dpdklab
2024-07-11 19:37 ` dpdklab
2024-07-11 19:39 ` dpdklab
2024-07-11 19:40 ` dpdklab
2024-07-11 19:43 ` dpdklab
2024-07-11 19:44 ` dpdklab
2024-07-11 19:44 ` dpdklab
2024-07-11 19:45 ` dpdklab
2024-07-11 19:47 ` |SUCCESS| " dpdklab
2024-07-11 19:49 ` |PENDING| " dpdklab
2024-07-11 19:50 ` dpdklab
2024-07-11 19:50 ` dpdklab
2024-07-11 19:51 ` dpdklab
2024-07-11 19:51 ` dpdklab
2024-07-11 19:55 ` dpdklab
2024-07-11 19:59 ` dpdklab
2024-07-11 20:02 ` dpdklab
2024-07-11 20:02 ` dpdklab
2024-07-11 20:06 ` |SUCCESS| " dpdklab
2024-07-11 20:07 ` |PENDING| " dpdklab
2024-07-11 20:08 ` dpdklab
2024-07-11 20:10 ` dpdklab
2024-07-11 20:11 ` dpdklab
2024-07-11 20:17 ` |SUCCESS| " dpdklab
2024-07-11 20:24 ` dpdklab
2024-07-11 22:20 ` dpdklab
2024-07-13  1:49 ` dpdklab
2024-07-14  6:53 ` dpdklab
2024-07-14 13:15 ` dpdklab
2024-07-14 21:47 ` dpdklab
2024-07-14 21:53 ` 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=669031af.050a0220.31dba.3c96SMTPIN_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).