From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw142363 [PATCH] [v3] net/virtio_user: fix cq descriptor c
Date: Fri, 12 Jul 2024 09:39:53 -0700 (PDT) [thread overview]
Message-ID: <66915c59.050a0220.1ae41.56bfSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240712123612.2389160-1-schalla@marvell.com>
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/142363
_Testing PASS_
Submitter: Srujana Challa <schalla@marvell.com>
Date: Friday, July 12 2024 12:36:12
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:9cbdb606e5d04de04be3d9f70f0e76551e8c9a36
142363 --> testing pass
Test environment and result as below:
+---------------------+----------------------+--------------------+-------------------+
| Environment | dpdk_mingw64_compile | dpdk_meson_compile | dpdk_msvc_compile |
+=====================+======================+====================+===================+
| Windows Server 2019 | PASS | PASS | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+
| Windows Server 2022 | PASS | PASS | PASS |
+---------------------+----------------------+--------------------+-------------------+
| FreeBSD 13.3 | SKIPPED | PASS | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+
| FreeBSD 14.1 | SKIPPED | PASS | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+
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
FreeBSD 13.3
Kernel: 13.3-RELEASE-p1
Compiler: clang 17.0.6
FreeBSD 14.1
Kernel: 14.1
Compiler: clang 18.1.5
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30506/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-07-12 16:39 UTC|newest]
Thread overview: 120+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240712123612.2389160-1-schalla@marvell.com>
2024-07-12 12:09 ` |SUCCESS| pw142363 [PATCH v3] net/virtio_user: fix cq descriptor conversion with non vDPA backend qemudev
2024-07-12 12:13 ` qemudev
2024-07-12 12:37 ` checkpatch
2024-07-12 13:23 ` 0-day Robot
2024-07-12 16:01 ` |SUCCESS| pw142363 [PATCH] [v3] net/virtio_user: fix cq descriptor c dpdklab
2024-07-12 16:06 ` dpdklab
2024-07-12 16:09 ` dpdklab
2024-07-12 16:09 ` dpdklab
2024-07-12 16:12 ` dpdklab
2024-07-12 16:15 ` dpdklab
2024-07-12 16:16 ` dpdklab
2024-07-12 16:19 ` dpdklab
2024-07-12 16:19 ` |PENDING| " dpdklab
2024-07-12 16:21 ` |SUCCESS| " dpdklab
2024-07-12 16:22 ` dpdklab
2024-07-12 16:22 ` |PENDING| " dpdklab
2024-07-12 16:22 ` |SUCCESS| " dpdklab
2024-07-12 16:23 ` dpdklab
2024-07-12 16:25 ` dpdklab
2024-07-12 16:26 ` dpdklab
2024-07-12 16:31 ` |PENDING| " dpdklab
2024-07-12 16:33 ` dpdklab
2024-07-12 16:34 ` dpdklab
2024-07-12 16:35 ` dpdklab
2024-07-12 16:38 ` dpdklab
2024-07-12 16:39 ` dpdklab
2024-07-12 16:39 ` dpdklab [this message]
2024-07-12 16:40 ` |SUCCESS| " dpdklab
2024-07-12 16:48 ` |PENDING| " dpdklab
2024-07-12 16:50 ` dpdklab
2024-07-12 16:52 ` dpdklab
2024-07-12 16:53 ` dpdklab
2024-07-12 16:53 ` dpdklab
2024-07-12 16:54 ` dpdklab
2024-07-12 16:55 ` dpdklab
2024-07-12 16:55 ` dpdklab
2024-07-12 16:56 ` dpdklab
2024-07-12 16:57 ` |SUCCESS| " dpdklab
2024-07-12 16:58 ` |PENDING| " dpdklab
2024-07-12 17:01 ` dpdklab
2024-07-12 17:02 ` dpdklab
2024-07-12 17:02 ` dpdklab
2024-07-12 17:04 ` dpdklab
2024-07-12 17:05 ` dpdklab
2024-07-12 17:05 ` dpdklab
2024-07-12 17:06 ` dpdklab
2024-07-12 17:07 ` dpdklab
2024-07-12 17:07 ` dpdklab
2024-07-12 17:08 ` dpdklab
2024-07-12 17:09 ` dpdklab
2024-07-12 17:10 ` dpdklab
2024-07-12 17:10 ` |SUCCESS| " dpdklab
2024-07-12 17:12 ` |PENDING| " dpdklab
2024-07-12 17:14 ` dpdklab
2024-07-12 17:17 ` dpdklab
2024-07-12 17:18 ` dpdklab
2024-07-12 17:19 ` dpdklab
2024-07-12 17:20 ` dpdklab
2024-07-12 17:20 ` dpdklab
2024-07-12 17:21 ` dpdklab
2024-07-12 17:23 ` dpdklab
2024-07-12 17:25 ` dpdklab
2024-07-12 17:27 ` dpdklab
2024-07-12 17:28 ` dpdklab
2024-07-12 17:28 ` dpdklab
2024-07-12 17:29 ` dpdklab
2024-07-12 17:30 ` dpdklab
2024-07-12 17:30 ` dpdklab
2024-07-12 17:31 ` dpdklab
2024-07-12 17:32 ` dpdklab
2024-07-12 17:33 ` dpdklab
2024-07-12 17:33 ` dpdklab
2024-07-12 17:33 ` dpdklab
2024-07-12 17:36 ` dpdklab
2024-07-12 17:36 ` dpdklab
2024-07-12 17:39 ` dpdklab
2024-07-12 17:42 ` dpdklab
2024-07-12 17:43 ` dpdklab
2024-07-12 17:46 ` dpdklab
2024-07-12 17:48 ` dpdklab
2024-07-12 17:49 ` dpdklab
2024-07-12 17:51 ` dpdklab
2024-07-12 17:51 ` |SUCCESS| " dpdklab
2024-07-12 17:53 ` |PENDING| " dpdklab
2024-07-12 17:54 ` dpdklab
2024-07-12 17:55 ` dpdklab
2024-07-12 17:56 ` dpdklab
2024-07-12 17:58 ` dpdklab
2024-07-12 18:05 ` dpdklab
2024-07-12 18:07 ` dpdklab
2024-07-12 18:09 ` |SUCCESS| " dpdklab
2024-07-12 18:10 ` |PENDING| " dpdklab
2024-07-12 18:10 ` dpdklab
2024-07-12 18:10 ` dpdklab
2024-07-12 18:11 ` dpdklab
2024-07-12 18:12 ` |SUCCESS| " dpdklab
2024-07-12 18:16 ` |PENDING| " dpdklab
2024-07-12 18:19 ` dpdklab
2024-07-12 18:21 ` dpdklab
2024-07-12 18:23 ` dpdklab
2024-07-12 18:24 ` dpdklab
2024-07-12 18:25 ` dpdklab
2024-07-12 18:25 ` dpdklab
2024-07-12 18:26 ` dpdklab
2024-07-12 18:28 ` dpdklab
2024-07-12 18:29 ` dpdklab
2024-07-12 18:31 ` dpdklab
2024-07-12 18:35 ` dpdklab
2024-07-12 18:36 ` dpdklab
2024-07-12 18:37 ` |SUCCESS| " dpdklab
2024-07-12 18:37 ` |PENDING| " dpdklab
2024-07-12 18:38 ` dpdklab
2024-07-12 18:40 ` dpdklab
2024-07-12 18:42 ` dpdklab
2024-07-12 19:44 ` |SUCCESS| " dpdklab
2024-07-12 20:44 ` dpdklab
2024-07-14 4:13 ` dpdklab
2024-07-14 11:56 ` dpdklab
2024-07-14 18:47 ` dpdklab
2024-07-14 18:54 ` 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=66915c59.050a0220.1ae41.56bfSMTPIN_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).