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, Chenbo Xia <chenbox@nvidia.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: |SUCCESS| pw157312 [PATCH] [v2] net/virtio-user: fix used ring addre
Date: Tue, 07 Oct 2025 08:38:18 -0700 (PDT)	[thread overview]
Message-ID: <68e533ea.050a0220.34a713.a7c2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251007144754.1690606-1-maxime.coquelin@redhat.com>

Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/157312

_Testing PASS_

Submitter: Maxime Coquelin <maxime.coquelin@redhat.com>
Date: Tuesday, October 07 2025 14:47:54 
DPDK git baseline: Repo:dpdk-next-virtio
  Branch: master
  CommitID:4159ea62922ce41566c7bab44655ad78bee85458

157312 --> testing pass

Upstream job id: Windows-Compile-DPDK-Native#31467

Test environment and result as below:

+---------------------+--------------------+-------------------+-------------------------+
|     Environment     | dpdk_meson_compile | dpdk_msvc_compile | dpdk_llvm_clang_compile |
+=====================+====================+===================+=========================+
| FreeBSD 14.2        | PASS               | SKIPPED           | SKIPPED                 |
+---------------------+--------------------+-------------------+-------------------------+
| Ubuntu 20.04        | PASS               | SKIPPED           | SKIPPED                 |
+---------------------+--------------------+-------------------+-------------------------+
| Windows Server 2022 | SKIPPED            | PASS              | PASS                    |
+---------------------+--------------------+-------------------+-------------------------+


FreeBSD 14.2
	Kernel: 14.2-RELEASE
	Compiler: clang 18.1.6

Ubuntu 20.04
	Kernel: 4.19
	Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-10-07 15:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251007144754.1690606-1-maxime.coquelin@redhat.com>
2025-10-07 14:14 ` |SUCCESS| pw157312 [PATCH v2] net/virtio-user: fix used ring address calculation qemudev
2025-10-07 14:19 ` qemudev
2025-10-07 14:48 ` |WARNING| " checkpatch
2025-10-07 15:09 ` |PENDING| pw157312 [PATCH] [v2] net/virtio-user: fix used ring addre dpdklab
2025-10-07 15:11 ` |SUCCESS| " dpdklab
2025-10-07 15:13 ` dpdklab
2025-10-07 15:21 ` |PENDING| " dpdklab
2025-10-07 15:26 ` dpdklab
2025-10-07 15:26 ` dpdklab
2025-10-07 15:31 ` |SUCCESS| " dpdklab
2025-10-07 15:37 ` dpdklab
2025-10-07 15:38 ` dpdklab [this message]
2025-10-07 15:52 ` dpdklab
2025-10-07 15:59 ` dpdklab
2025-10-07 16:02 ` dpdklab
2025-10-07 16:04 ` dpdklab
2025-10-07 16:27 ` dpdklab
2025-10-07 16:30 ` dpdklab
2025-10-07 16:59 ` 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=68e533ea.050a0220.34a713.a7c2SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=chenbox@nvidia.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=maxime.coquelin@redhat.com \
    --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).