From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: thuth@redhat.com, alistair.francis@wdc.com, groug@kaod.org,
peter.maydell@linaro.org,
Daniel Henrique Barboza <dbarboza@ventanamicro.com>,
Daniel Henrique Barboza <dbarboza@ventanamicro.com>
Subject: Re: [PATCH for-9.0 v3 0/2] qtest/virtio-9p-test.c: fix slow tests
Date: Wed, 27 Mar 2024 19:53:42 +0100 [thread overview]
Message-ID: <3153513.lVJF6dkNTK@silver> (raw)
In-Reply-To: <20240327142011.805728-1-dbarboza@ventanamicro.com>
On Wednesday, March 27, 2024 3:20:09 PM CET Daniel Henrique Barboza wrote:
> Hi,
>
> In this new version we took a different approach after the discussions
> we had in [1]. The tests are now untouched, and we're addressing the root
> cause directly: the fact that we have a single temp dir for all the test
> execution in qos-test.
>
> We're now creating and cleaning temp dirs for each individual test by
> calling virtio_9p_create_local_test_dir() in the .before callback for
> the local 9p tests (assign_9p_local_driver()). In this same callback we
> queue the cleanup function that will erase the created temp dir. The
> cleanup will run after the test ran successfully.
>
> This approach is similar to what other qtests do (in fact this design was
> taken from vhost-user-test.c) so it's not like we're doing something
> novel.
>
> I kept the revert of the slow test gate because Gitlab seems to approve
> it:
>
> https://gitlab.com/danielhb/qemu/-/pipelines/1229836634
>
> Feel free to take just patch 1 if we're not sure about re-enabling these
> tests in Gitlab.
>
>
> Changes from v3:
> - patches 1 to 6: dropped
> - patch 1 (new):
> - create and remove temporary dirs on each test
> - v2 link: https://mail.gnu.org/archive/html/qemu-devel/2024-03/msg06335.html
>
> [1] https://mail.gnu.org/archive/html/qemu-devel/2024-03/msg06400.html
>
> Daniel Henrique Barboza (2):
> qtest/virtio-9p-test.c: create/remove temp dirs after each test
> qtest/virtio-9p-test.c: remove g_test_slow() gate
>
> tests/qtest/virtio-9p-test.c | 32 +++++++++++---------------------
> 1 file changed, 11 insertions(+), 21 deletions(-)
>
>
Awesome!
Reviewed-by: Christian Schoenebeck <qemu_oss@crudebyte.com>
Are the riscv patches already on master? I.e. should I push those two patches
through my queue?
/Christian
next prev parent reply other threads:[~2024-03-27 18:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 14:20 [PATCH for-9.0 v3 0/2] qtest/virtio-9p-test.c: fix slow tests Daniel Henrique Barboza
2024-03-27 14:20 ` [PATCH for-9.0 v3 1/2] qtest/virtio-9p-test.c: create/remove temp dirs after each test Daniel Henrique Barboza
2024-03-27 14:20 ` [PATCH for-9.0 v3 2/2] qtest/virtio-9p-test.c: remove g_test_slow() gate Daniel Henrique Barboza
2024-04-16 19:54 ` Michael Tokarev
2024-04-16 23:16 ` Daniel Henrique Barboza
2024-04-17 11:52 ` Christian Schoenebeck
2024-04-17 12:20 ` Daniel P. Berrangé
2024-03-27 14:56 ` [PATCH for-9.0 v3 0/2] qtest/virtio-9p-test.c: fix slow tests Greg Kurz
2024-03-27 18:53 ` Christian Schoenebeck [this message]
2024-03-27 19:41 ` Daniel Henrique Barboza
2024-03-28 6:23 ` Thomas Huth
2024-03-28 9:12 ` Christian Schoenebeck
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=3153513.lVJF6dkNTK@silver \
--to=qemu_oss@crudebyte.com \
--cc=alistair.francis@wdc.com \
--cc=dbarboza@ventanamicro.com \
--cc=groug@kaod.org \
--cc=peter.maydell@linaro.org \
--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 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.