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: |SUCCESS| pw153864 [PATCH] [v1,1/1] vhost: handle virtqueue locking
Date: Thu, 29 May 2025 22:47:34 -0700 (PDT)	[thread overview]
Message-ID: <68394676.050a0220.1aaa76.8822SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250529123226.1875075-2-dvo-plv@napatech.com>

Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/153864

_Testing PASS_

Submitter: Danylo Vodopianov <dvo-plv@napatech.com>
Date: Thursday, May 29 2025 12:32:26 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:3223019e73391066cbb0d248051b163e5373034c

153864 --> testing pass

Upstream job id: Generic-DPDK-Compile-Meson#392713

Test environment and result as below:

+------------------------------+--------------------+
|         Environment          | dpdk_meson_compile |
+==============================+====================+
| Red Hat Enterprise Linux 9.5 | PASS               |
+------------------------------+--------------------+
| Ubuntu 20.04                 | PASS               |
+------------------------------+--------------------+
| Debian GNU/Linux 12          | PASS               |
+------------------------------+--------------------+
| Fedora 40 (ARM)              | PASS               |
+------------------------------+--------------------+
| Fedora 40 (ARM Clang)        | PASS               |
+------------------------------+--------------------+
| Fedora 41 (ARM)              | PASS               |
+------------------------------+--------------------+
| Fedora 41 (ARM Clang)        | PASS               |
+------------------------------+--------------------+
| Ubuntu 22.04                 | PASS               |
+------------------------------+--------------------+
| Ubuntu 24.04                 | PASS               |
+------------------------------+--------------------+
| CentOS Stream 9 (ARM)        | PASS               |
+------------------------------+--------------------+
| CentOS Stream 10 (ARM)       | PASS               |
+------------------------------+--------------------+


Red Hat Enterprise Linux 9.5
	Kernel: 5.4
	Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-2)

Ubuntu 20.04
	Kernel: 5.15
	Compiler: aarch64-linux-gnu-gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

Debian GNU/Linux 12
	Kernel: 5.4
	Compiler: gcc gcc (Debian 12.2.0-14) 12.2.0

Fedora 40 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)

Fedora 40 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.8 (Fedora 18.1.8-1.fc40)

Fedora 41 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)

Fedora 41 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 19.1.5 (Fedora 19.1.5-1.fc41)

Ubuntu 22.04
	Kernel: 5.4
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Ubuntu 24.04
	Kernel: 5.4
	Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0

CentOS Stream 9 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)

CentOS Stream 10 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20241104 (Red Hat 14.2.1-6)

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-05-30  5:47 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250529123226.1875075-2-dvo-plv@napatech.com>
2025-05-29 12:07 ` |SUCCESS| pw153864 [PATCH v1 1/1] vhost: handle virtqueue locking for memory hotplug qemudev
2025-05-29 12:11 ` qemudev
2025-05-29 12:32 ` |WARNING| " checkpatch
2025-05-29 13:43 ` |SUCCESS| " 0-day Robot
2025-05-29 20:49 ` |SUCCESS| pw153864 [PATCH] [v1,1/1] vhost: handle virtqueue locking dpdklab
2025-05-29 21:09 ` |PENDING| " dpdklab
2025-05-29 21:26 ` |SUCCESS| " dpdklab
2025-05-29 21:53 ` dpdklab
2025-05-29 21:57 ` dpdklab
2025-05-29 21:59 ` dpdklab
2025-05-29 22:00 ` dpdklab
2025-05-29 22:13 ` |PENDING| " dpdklab
2025-05-29 22:13 ` dpdklab
2025-05-29 22:20 ` |SUCCESS| " dpdklab
2025-05-29 22:21 ` dpdklab
2025-05-29 23:04 ` dpdklab
2025-05-30  0:21 ` dpdklab
2025-05-30  1:01 ` |PENDING| " dpdklab
2025-05-30  1:28 ` dpdklab
2025-05-30  1:34 ` |SUCCESS| " dpdklab
2025-05-30  1:35 ` dpdklab
2025-05-30  1:36 ` |PENDING| " dpdklab
2025-05-30  1:41 ` |SUCCESS| " dpdklab
2025-05-30  1:55 ` dpdklab
2025-05-30  2:44 ` |PENDING| " dpdklab
2025-05-30  3:53 ` |WARNING| " dpdklab
2025-05-30  3:54 ` dpdklab
2025-05-30  3:54 ` dpdklab
2025-05-30  3:54 ` dpdklab
2025-05-30  3:55 ` dpdklab
2025-05-30  4:44 ` dpdklab
2025-05-30  5:47 ` dpdklab [this message]
2025-05-30  5:49 ` |SUCCESS| " dpdklab
2025-05-30  8:29 ` dpdklab
2025-05-30  9:18 ` dpdklab
2025-05-30  9:51 ` |WARNING| " dpdklab
2025-05-30 21:54 ` dpdklab
2025-05-30 22:02 ` dpdklab
2025-05-30 23:06 ` |SUCCESS| " dpdklab
2025-05-30 23:43 ` dpdklab
2025-05-31  2:11 ` dpdklab
2025-05-31  2:23 ` dpdklab
2025-05-31  2:36 ` dpdklab
2025-05-31  2:45 ` dpdklab
2025-06-04 13:11 ` dpdklab
2025-06-04 13:27 ` 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=68394676.050a0220.1aaa76.8822SMTPIN_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).