From: Fiona Ebner <f.ebner@proxmox.com>
To: Dominik Csapak <d.csapak@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH qemu-server 2/6] tests: hotplug: add some test cases
Date: Mon, 14 Sep 2026 10:09:31 +0200 [thread overview]
Message-ID: <16b8427f-e5bd-4672-ad16-1cab834891a0@proxmox.com> (raw)
In-Reply-To: <dfd22110-426d-4986-8369-1c2f13d8e32a@proxmox.com>
Am 11.09.26 um 12:11 PM schrieb Dominik Csapak:
> On 9/10/26 4:24 PM, Fiona Ebner wrote:
>> Am 10.09.26 um 1:29 PM schrieb Dominik Csapak:
>>> +
>>> +# resulting config
>>> +arch: aarch64
>>> +bios: ovmf
>>> +bootdisk: scsi0
>>> +cores: 2
>>> +efidisk0: local:8006/vm-8006-disk-2.qcow2,efitype=4m
>>> +memory: 2048
>>> +name: hotplug
>>> +net0: virtio=A2:C0:43:77:08:A0,bridge=vmbr0
>>> +ostype: l26
>>> +scsi0: local:8006/vm-8006-disk-0.qcow2,size=32G
>>> +scsihw: virtio-scsi-pci
>>> +smbios1: uuid=7b10d7af-b932-4c66-b2c3-3996152ec465
>>> +sockets: 1
>>> +virtio1: local:8006/vm-8006-disk-1.qcow2,iothread=1,size=32G
>>> +vmgenid: c773c261-d800-4348-9f5d-167fadd53cf8
>>
>> Would just recording and the changes be more sensible to avoid lots of
>> redundant information? That could also already live in the test
>> definition with the test runner checking that nothing additional is
>> changed. In most cases it will directly overlap with what is in
>> [PENDING], so you don't even need to specify any additional expected
>> changes.
>>
>> What do you think?
>
> what about not recording the resulting config at all as an expected
> file, but simply check in the test if there is still a
> [PENDING] section, mark tests where this is expected and
> fail where this is not the case?
>
> then we could have a simple file with the recorded qmp/hmp calls
> in a list without any comment structure
Yeah, sounds good too :)
next prev parent reply other threads:[~2026-09-14 8:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 11:00 [PATCH qemu-server 0/6] add hotplug tests and fix uncovered bugs Dominik Csapak
2026-09-10 11:00 ` [PATCH qemu-server 1/6] tests: hotplug: add initial hotplug test harness Dominik Csapak
2026-09-10 14:24 ` Fiona Ebner
2026-09-11 10:08 ` Dominik Csapak
2026-09-14 8:05 ` Fiona Ebner
2026-09-10 11:00 ` [PATCH qemu-server 2/6] tests: hotplug: add some test cases Dominik Csapak
2026-09-10 14:24 ` Fiona Ebner
2026-09-11 10:11 ` Dominik Csapak
2026-09-14 8:09 ` Fiona Ebner [this message]
2026-09-10 11:00 ` [PATCH qemu-server 3/6] tests: hotplug: add cases for known defects Dominik Csapak
2026-09-10 11:00 ` [PATCH qemu-server 4/6] tests: hotplug: add test case for adding scsi14 on qemu 11.1 Dominik Csapak
2026-09-10 11:00 ` [PATCH qemu-server 5/6] hotplug: fix vm_deviceplug call for 'tablet' and 'keyboard' on aarch64 Dominik Csapak
2026-09-10 11:00 ` [PATCH qemu-server 6/6] hotplug: remove iothread if adding drive device failed Dominik Csapak
2026-09-14 8:58 ` superseded: [PATCH qemu-server 0/6] add hotplug tests and fix uncovered bugs Dominik Csapak
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=16b8427f-e5bd-4672-ad16-1cab834891a0@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=d.csapak@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.