From: patchwork-bot+netdevbpf@kernel.org
To: Bobby Eshleman <bobbyeshleman@gmail.com>
Cc: sgarzare@redhat.com, shuah@kernel.org,
virtualization@lists.linux.dev, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
horms@kernel.org, bobbyeshleman@meta.com
Subject: Re: [PATCH net-next v4 00/12] selftests/vsock: refactor and improve vmtest infrastructure
Date: Wed, 12 Nov 2025 14:30:23 +0000 [thread overview]
Message-ID: <176295782301.29085.14486251281449214538.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251108-vsock-selftests-fixes-and-improvements-v4-0-d5e8d6c87289@meta.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 08 Nov 2025 08:00:51 -0800 you wrote:
> Hey all,
>
> This patch series refactors the vsock selftest VM infrastructure to
> improve test run times, improve logging, and prepare for future tests
> which make heavy usage of these refactored functions and have new
> requirements such as simultaneous QEMU processes.
>
> [...]
Here is the summary with links:
- [net-next,v4,01/12] selftests/vsock: improve logging in vmtest.sh
https://git.kernel.org/netdev/net-next/c/d9cac93cd1be
- [net-next,v4,02/12] selftests/vsock: make wait_for_listener() work even if pipefail is on
https://git.kernel.org/netdev/net-next/c/2ed3ce7efbd2
- [net-next,v4,03/12] selftests/vsock: reuse logic for vsock_test through wrapper functions
https://git.kernel.org/netdev/net-next/c/4f76ff14d3d9
- [net-next,v4,04/12] selftests/vsock: avoid multi-VM pidfile collisions with QEMU
https://git.kernel.org/netdev/net-next/c/ac8997e943bc
- [net-next,v4,05/12] selftests/vsock: do not unconditionally die if qemu fails
https://git.kernel.org/netdev/net-next/c/c7df4adc0679
- [net-next,v4,06/12] selftests/vsock: speed up tests by reducing the QEMU pidfile timeout
https://git.kernel.org/netdev/net-next/c/9e2ad0bc3640
- [net-next,v4,07/12] selftests/vsock: add check_result() for pass/fail counting
https://git.kernel.org/netdev/net-next/c/7fea50dff988
- [net-next,v4,08/12] selftests/vsock: identify and execute tests that can re-use VM
https://git.kernel.org/netdev/net-next/c/d13fb04a4bf0
- [net-next,v4,09/12] selftests/vsock: add BUILD=0 definition
https://git.kernel.org/netdev/net-next/c/592e3d14cecf
- [net-next,v4,10/12] selftests/vsock: add 1.37 to tested virtme-ng versions
https://git.kernel.org/netdev/net-next/c/67422ef38f8c
- [net-next,v4,11/12] selftests/vsock: add vsock_loopback module loading
https://git.kernel.org/netdev/net-next/c/338c5ddf4c88
- [net-next,v4,12/12] selftests/vsock: disable shellcheck SC2317 and SC2119
https://git.kernel.org/netdev/net-next/c/99f932c90509
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-11-12 14:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-08 16:00 [PATCH net-next v4 00/12] selftests/vsock: refactor and improve vmtest infrastructure Bobby Eshleman
2025-11-08 16:00 ` [PATCH net-next v4 01/12] selftests/vsock: improve logging in vmtest.sh Bobby Eshleman
2025-11-12 11:15 ` Stefano Garzarella
2025-11-08 16:00 ` [PATCH net-next v4 02/12] selftests/vsock: make wait_for_listener() work even if pipefail is on Bobby Eshleman
2025-11-12 11:15 ` Stefano Garzarella
2025-11-08 16:00 ` [PATCH net-next v4 03/12] selftests/vsock: reuse logic for vsock_test through wrapper functions Bobby Eshleman
2025-11-12 11:19 ` Stefano Garzarella
2025-11-08 16:00 ` [PATCH net-next v4 04/12] selftests/vsock: avoid multi-VM pidfile collisions with QEMU Bobby Eshleman
2025-11-12 11:22 ` Stefano Garzarella
2025-11-08 16:00 ` [PATCH net-next v4 05/12] selftests/vsock: do not unconditionally die if qemu fails Bobby Eshleman
2025-11-12 11:23 ` Stefano Garzarella
2025-11-08 16:00 ` [PATCH net-next v4 06/12] selftests/vsock: speed up tests by reducing the QEMU pidfile timeout Bobby Eshleman
2025-11-12 11:24 ` Stefano Garzarella
2025-11-08 16:00 ` [PATCH net-next v4 07/12] selftests/vsock: add check_result() for pass/fail counting Bobby Eshleman
2025-11-12 11:24 ` Stefano Garzarella
2025-11-08 16:00 ` [PATCH net-next v4 08/12] selftests/vsock: identify and execute tests that can re-use VM Bobby Eshleman
2025-11-12 11:27 ` Stefano Garzarella
2025-11-08 16:01 ` [PATCH net-next v4 09/12] selftests/vsock: add BUILD=0 definition Bobby Eshleman
2025-11-12 11:27 ` Stefano Garzarella
2025-11-08 16:01 ` [PATCH net-next v4 10/12] selftests/vsock: add 1.37 to tested virtme-ng versions Bobby Eshleman
2025-11-08 16:01 ` [PATCH net-next v4 11/12] selftests/vsock: add vsock_loopback module loading Bobby Eshleman
2025-11-08 16:01 ` [PATCH net-next v4 12/12] selftests/vsock: disable shellcheck SC2317 and SC2119 Bobby Eshleman
2025-11-12 11:28 ` Stefano Garzarella
2025-11-11 12:33 ` [PATCH net-next v4 00/12] selftests/vsock: refactor and improve vmtest infrastructure Paolo Abeni
2025-11-12 11:29 ` Stefano Garzarella
2025-11-12 14:30 ` patchwork-bot+netdevbpf [this message]
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=176295782301.29085.14486251281449214538.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bobbyeshleman@gmail.com \
--cc=bobbyeshleman@meta.com \
--cc=horms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sgarzare@redhat.com \
--cc=shuah@kernel.org \
--cc=virtualization@lists.linux.dev \
/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