From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
Greg Kurz <groug@kaod.org>
Subject: Re: [PATCH v3 0/2] 9pfs: test suite fixes
Date: Sun, 01 Nov 2020 20:17:50 +0100 [thread overview]
Message-ID: <2977702.F8LXnbqENp@silver> (raw)
In-Reply-To: <061f1d9c-86d8-76b9-b868-59749542d9a2@ilande.co.uk>
On Sonntag, 1. November 2020 19:02:28 CET Mark Cave-Ayland wrote:
> On 01/11/2020 15:12, Christian Schoenebeck wrote:
> > Fixes test failures with the 9pfs 'local' tests as discussed with latest
> > 9P PR. See the discussion of that PR v2 (Fri, Oct 30th) for details.
> >
> > In conjunction with Peter Xu's two migration patches (fixing occasional
> > lockups of migration tests) overall situation appears to be smooth now:
> > https://lore.kernel.org/qemu-devel/20201030135350.GA588069@xz-x1/
> >
> > v2->v3:
> > - Make the two functions for creating and removing the 9pfs test
> > directory
> >
> > public [NEW patch 1].
> >
> > - Place the constructor and destructor functions in virtio-9p-test.c,
> > not
> >
> > in virtio-9p.c, because the latter location would cause the
> > constructor
> > to be executed whenever libqos is loaded, which would break other,
> > completely unrelated tests suites that just link to libqos [patch 2].
> >
> > - Previous patch 2 (coverity fix) is already queued, no changes, hence
> >
> > omitted in this v3.
> >
> > v1->v2:
> > - Added Greg's tested-by tag [patch 1].
> >
> > - Log an info-level message if mkdir() failed [patch 2].
> >
> > - Update commit log message about coverity being the reporter and
> >
> > details of the coverity report [patch 2].
> >
> > Christian Schoenebeck (2):
> > tests/9pfs: make create/remove test dir public
> > tests/9pfs: fix test dir for parallel tests
> >
> > tests/qtest/libqos/virtio-9p.c | 20 ++++++++++----------
> > tests/qtest/libqos/virtio-9p.h | 10 ++++++++++
> > tests/qtest/virtio-9p-test.c | 12 ++++++++++++
> > 3 files changed, 32 insertions(+), 10 deletions(-)
>
> FWIW one thing I've noticed recently is that my builds for
> qemu-system-sparc64 have started giving this warning about a missing
> "qtest-9p-local" directory during make check:
>
> ...
> ...
> Running test QAPI schema regression tests
> Running test qtest-sparc64/endianness-test
> Running test qtest-sparc64/prom-env-test
> Running test qtest-sparc64/boot-serial-test
> Running test qtest-sparc64/cdrom-test
> Running test qtest-sparc64/device-introspect-test
> Running test qtest-sparc64/machine-none-test
> Running test qtest-sparc64/qmp-test
> Running test qtest-sparc64/qmp-cmd-test
> Running test qtest-sparc64/qom-test
> Running test qtest-sparc64/test-hmp
> Running test qtest-sparc64/qos-test
> rm: cannot remove '/home/build/src/qemu/git/qemu/build/qtest-9p-local': No
> such file or directory
> TEST iotest-qcow2: 001
> TEST iotest-qcow2: 002
> TEST iotest-qcow2: 003
> TEST iotest-qcow2: 004
> TEST iotest-qcow2: 005
> ...
> ...
>
> Would this get resolved by the changes to the test directory in this
> patchset? The build is a simple configure run with
> "--target-list=sparc64-softmmu".
>
>
> ATB,
>
> Mark.
Yes, that should be resolved with the next 9p PR as well, additionally with
the following patch that is:
https://github.com/cschoenebeck/qemu/commit/603cc76a6069
Thanks for the feedback!
Best regards,
Christian Schoenebeck
next prev parent reply other threads:[~2020-11-01 19:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 15:12 [PATCH v3 0/2] 9pfs: test suite fixes Christian Schoenebeck
2020-11-01 14:25 ` [PATCH v3 1/2] tests/9pfs: make create/remove test dir public Christian Schoenebeck
2020-11-01 17:03 ` Greg Kurz
2020-11-01 14:37 ` [PATCH v3 2/2] tests/9pfs: fix test dir for parallel tests Christian Schoenebeck
2020-11-01 17:44 ` Greg Kurz
2020-11-01 19:14 ` Christian Schoenebeck
2020-11-01 19:31 ` Greg Kurz
2020-11-01 18:02 ` [PATCH v3 0/2] 9pfs: test suite fixes Mark Cave-Ayland
2020-11-01 19:17 ` Christian Schoenebeck [this message]
2020-11-01 19:35 ` Mark Cave-Ayland
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=2977702.F8LXnbqENp@silver \
--to=qemu_oss@crudebyte.com \
--cc=groug@kaod.org \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=qemu-devel@nongnu.org \
/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.