From: Laurent Vivier <lvivier@redhat.com>
To: Thomas Huth <thuth@redhat.com>, Fabiano Rosas <farosas@suse.de>,
qemu-devel@nongnu.org
Cc: Amit Shah <amit@kernel.org>, Paolo Bonzini <pbonzini@redhat.com>,
Emanuele Giuseppe Esposito <e.emanuelegiuseppe@gmail.com>
Subject: Re: [PATCH 04/12] tests/qtest: Skip virtio-serial-console tests if device not present
Date: Tue, 7 Feb 2023 16:35:05 +0100 [thread overview]
Message-ID: <79b5fb1f-f377-0fb1-0abf-8454e1f2cd91@redhat.com> (raw)
In-Reply-To: <3b2e6eb7-2f0a-7663-b454-bce49d92f36f@redhat.com>
On 2/7/23 14:25, Thomas Huth wrote:
> On 06/02/2023 16.04, Fabiano Rosas wrote:
>> The virtconsole device might not be present in the QEMU build that is
>> being tested. Skip the test if that's the case.
>>
>> Signed-off-by: Fabiano Rosas <farosas@suse.de>
>> ---
>> tests/qtest/virtio-serial-test.c | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/tests/qtest/virtio-serial-test.c b/tests/qtest/virtio-serial-test.c
>> index 2541034822..f4e05e8fdd 100644
>> --- a/tests/qtest/virtio-serial-test.c
>> +++ b/tests/qtest/virtio-serial-test.c
>> @@ -28,6 +28,10 @@ static void register_virtio_serial_test(void)
>> {
>> QOSGraphTestOptions opts = { };
>> + if (!qtest_has_device("virtconsole")) {
>> + return;
>> + }
>> +
>> opts.edge.before_cmd_line = "-device virtconsole,bus=vser0.0";
>> qos_add_test("console-nop", "virtio-serial", virtio_serial_nop, &opts);
>
> virtio-serial-test.c is a qos test - and this should detect automatically already whether
> a device is available and pluggable or not, I think.
>
> There must be something else wrong here ... Laurent, Paolo, any ideas?
I think the checking of the device should be added where the device is added to the qos
tree, in libqos/virtio-serial.c
If you don't add the device then the test is not started.
If I remember correctly, there was no autodetection of the devices, all are added statically.
Thanks,
Laurent
next prev parent reply other threads:[~2023-02-07 15:36 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 15:04 [PATCH 00/12] qtests vs. default devices Fabiano Rosas
2023-02-06 15:04 ` [PATCH 01/12] tests/qtest: Skip PXE tests for missing devices Fabiano Rosas
2023-02-07 13:14 ` Thomas Huth
2023-02-06 15:04 ` [PATCH 02/12] tests/qtest: Do not run lsi53c895a test if device is not present Fabiano Rosas
2023-02-06 15:31 ` Philippe Mathieu-Daudé
2023-02-06 17:46 ` Fabiano Rosas
2023-02-06 18:52 ` Philippe Mathieu-Daudé
2023-02-07 13:12 ` Thomas Huth
2023-02-07 14:02 ` Fabiano Rosas
2023-02-07 14:12 ` Thomas Huth
2023-02-06 15:04 ` [PATCH 03/12] tests/qtest: Add dependence on PCIE_ROOT for virtio-net-failover.c Fabiano Rosas
2023-02-07 13:22 ` Thomas Huth
2023-02-07 15:02 ` Fabiano Rosas
2023-02-06 15:04 ` [PATCH 04/12] tests/qtest: Skip virtio-serial-console tests if device not present Fabiano Rosas
2023-02-07 13:25 ` Thomas Huth
2023-02-07 15:35 ` Laurent Vivier [this message]
2023-02-07 13:37 ` Thomas Huth
2023-02-06 15:04 ` [PATCH 05/12] tests/qtest: hd-geo-test: Check for missing devices Fabiano Rosas
2023-02-07 13:52 ` Thomas Huth
2023-02-06 15:04 ` [PATCH 06/12] tests/qtest: Skip unplug tests that use " Fabiano Rosas
2023-02-07 13:59 ` Thomas Huth
2023-02-07 14:17 ` Fabiano Rosas
2023-02-07 14:22 ` Thomas Huth
2023-02-06 15:04 ` [PATCH 07/12] tests/qtest: drive_del-test: Skip tests that require " Fabiano Rosas
2023-02-07 14:20 ` Thomas Huth
2023-02-07 14:32 ` Fabiano Rosas
2023-02-06 15:04 ` [PATCH 08/12] tests/qtest: Check for devices in bios-tables-test Fabiano Rosas
2023-02-06 15:21 ` Michael S. Tsirkin
2023-02-06 15:04 ` [PATCH 09/12] tests/qtest: Do not include hexloader-test if loader device is not present Fabiano Rosas
2023-02-07 14:30 ` Thomas Huth
2023-02-06 15:04 ` [PATCH 10/12] tests/qemu-iotests: Require virtio-scsi-pci Fabiano Rosas
2023-02-07 14:32 ` Thomas Huth
2023-02-06 15:04 ` [PATCH 11/12] tests/qtest: bios-tables-test: Skip if missing configs Fabiano Rosas
2023-02-07 14:35 ` Thomas Huth
2023-02-07 14:42 ` Michael S. Tsirkin
2023-02-08 10:52 ` Igor Mammedov
2023-02-08 14:25 ` Michael S. Tsirkin
2023-02-06 15:04 ` [PATCH 12/12] [NOT FOR MERGE] tests/qtest: Introduce qtest_validate_args Fabiano Rosas
2023-02-07 14:55 ` Thomas Huth
2023-02-07 15:35 ` Fabiano Rosas
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=79b5fb1f-f377-0fb1-0abf-8454e1f2cd91@redhat.com \
--to=lvivier@redhat.com \
--cc=amit@kernel.org \
--cc=e.emanuelegiuseppe@gmail.com \
--cc=farosas@suse.de \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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;
as well as URLs for NNTP newsgroup(s).