From: Fiona Ebner <f.ebner@proxmox.com>
To: Alexandre Derumier via pve-devel <pve-devel@lists.proxmox.com>
Subject: [pve-devel] applied: [PATCH qemu-server] tests: add cache && aio tests for differents storage type
Date: Wed, 11 Jun 2025 10:08:50 +0200 [thread overview]
Message-ID: <174962916534.17755.13916376886792772938.b4-ty@proxmox.com> (raw)
In-Reply-To: <mailman.286.1749207110.395.pve-devel@lists.proxmox.com>
Applied, thanks! I renamed the volume group to avoid using the same
name as the already existing lvm-thin storage. I also had already
written a test for this with a single config and applied that too,
as it better covers the local storage case.
[1/1] tests: add cache && aio tests for differents storage type
commit: 1d8794500722d9aaae8a43905682ecf66a7f2323
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-06-11 8:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 10:51 [pve-devel] " Alexandre Derumier via pve-devel
2025-06-11 8:08 ` Fiona Ebner [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=174962916534.17755.13916376886792772938.b4-ty@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/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