From: Thomas Huth <thuth@redhat.com>
To: Lukas Straub <lukasstraub2@web.de>, qemu-devel <qemu-devel@nongnu.org>
Cc: Laurent Vivier <lvivier@redhat.com>,
Marc-Andre Lureau <marcandre.lureau@gmail.com>,
Li Zhang <zhlcindy@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH 1/5] tests: Use the normal yank code instead of stubs in relevant tests
Date: Mon, 22 Mar 2021 06:20:50 +0100 [thread overview]
Message-ID: <1fc6eff2-a8e5-4ae2-96a5-1b30325dff81@redhat.com> (raw)
In-Reply-To: <950007e82e19e75831b29fac07ab990c213d2352.1616368879.git.lukasstraub2@web.de>
On 22/03/2021 00.31, Lukas Straub wrote:
> Use the normal yank code instead of stubs in relevant tests to
> increase coverage and to ensure that registering and unregistering
> of yank instances and functions is done correctly.
>
> Signed-off-by: Lukas Straub <lukasstraub2@web.de>
> ---
> tests/qtest/meson.build | 6 +++---
> tests/unit/meson.build | 4 ++--
> 2 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/tests/qtest/meson.build b/tests/qtest/meson.build
> index 66ee9fbf45..40e1f495f7 100644
> --- a/tests/qtest/meson.build
> +++ b/tests/qtest/meson.build
> @@ -234,9 +234,9 @@ tpmemu_files = ['tpm-emu.c', 'tpm-util.c', 'tpm-tests.c']
> qtests = {
> 'bios-tables-test': [io, 'boot-sector.c', 'acpi-utils.c', 'tpm-emu.c'],
> 'cdrom-test': files('boot-sector.c'),
> - 'dbus-vmstate-test': files('migration-helpers.c') + dbus_vmstate1,
> + 'dbus-vmstate-test': ['migration-helpers.c', dbus_vmstate1, '../../monitor/yank.c'],
> 'ivshmem-test': [rt, '../../contrib/ivshmem-server/ivshmem-server.c'],
> - 'migration-test': files('migration-helpers.c'),
> + 'migration-test': ['migration-helpers.c', io, '../../monitor/yank.c'],
> 'pxe-test': files('boot-sector.c'),
> 'qos-test': [chardev, io, qos_test_ss.apply(config_host, strict: false).sources()],
> 'tpm-crb-swtpm-test': [io, tpmemu_files],
Is this really necessary for the qtests? I can understand the change for the
unit tests, but the qtests are separate programs where I could not imagine
that they use the yank functions in any way?
Thomas
PS: Please add a proper description about the yank feature to either that
yank.c file or to include/qemu/yank.h ... I had a hard time to find out what
this code is all about until I finally looked up your cover letter of the
original series on the mailing list.
next prev parent reply other threads:[~2021-03-22 5:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-21 23:31 [PATCH 0/5] yank: Add chardev tests and fixes Lukas Straub
2021-03-21 23:31 ` [PATCH 1/5] tests: Use the normal yank code instead of stubs in relevant tests Lukas Straub
2021-03-22 5:20 ` Thomas Huth [this message]
2021-03-22 7:35 ` Lukas Straub
2021-03-22 16:00 ` Thomas Huth
2021-03-22 17:48 ` Lukas Straub
2021-03-23 4:46 ` Thomas Huth
2021-03-23 14:54 ` Lukas Straub
2021-03-21 23:31 ` [PATCH 2/5] tests: Add tests for yank with the chardev-change Lukas Straub
2021-03-22 8:04 ` Marc-André Lureau
2021-03-21 23:31 ` [PATCH 3/5] chardev/char.c: Move object_property_try_add_child out of chardev_new Lukas Straub
2021-03-22 8:42 ` Marc-André Lureau
2021-03-21 23:31 ` [PATCH 4/5] chardev/char.c: Always pass id to chardev_new Lukas Straub
2021-03-22 8:33 ` Marc-André Lureau
2021-03-22 10:32 ` Li Zhang
2021-03-21 23:32 ` [PATCH 5/5] chardev: Fix yank with the chardev-change case Lukas Straub
2021-03-22 8:32 ` Marc-André Lureau
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=1fc6eff2-a8e5-4ae2-96a5-1b30325dff81@redhat.com \
--to=thuth@redhat.com \
--cc=lukasstraub2@web.de \
--cc=lvivier@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=zhlcindy@gmail.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).