From: "Daniel P. Berrange" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] vhost-user: disable broken test
Date: Tue, 5 Sep 2017 18:17:46 +0100 [thread overview]
Message-ID: <20170905171746.GI311@redhat.com> (raw)
In-Reply-To: <20170905170822.9109-1-f4bug@amsat.org>
On Tue, Sep 05, 2017 at 02:08:22PM -0300, Philippe Mathieu-Daudé wrote:
> tests/vhost-user-test keeps failing on build-system since Aug 15:
>
> ERROR:tests/vhost-user-test.c:835:test_flags_mismatch: child process (/i386/vhost-user/flags-mismatch/subprocess [4836]) failed unexpectedly
> ...
> ERROR:tests/vhost-user-test.c:807:test_connect_fail: child process (/x86_64/vhost-user/connect-fail/subprocess [58910]) failed unexpectedly
Seems like it is always the subprocess tests which fail
from what I see. So rather than disable the entire test,
just put
if (1) {
g_test_skip("Skipping unreliable subprocess test");
return;
}
at the top of each test_*_subprocess() method
>
> The test can still be build for debug session using:
>
> $ FORCE_VHOST_USER_NET_TEST=1 ./configure ...
>
> Suggested-by: Peter Maydell <peter.maydell@linaro.org>
> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> ---
> configure | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/configure b/configure
> index fb7e34a901..d3b895b167 100755
> --- a/configure
> +++ b/configure
> @@ -6386,7 +6386,12 @@ if supported_kvm_target $target; then
> if test "$vhost_net" = "yes" ; then
> echo "CONFIG_VHOST_NET=y" >> $config_target_mak
> if test "$vhost_user" = "yes" ; then
> - echo "CONFIG_VHOST_USER_NET_TEST_$target_name=y" >> $config_host_mak
> + if test -n "${FORCE_VHOST_USER_NET_TEST}"; then
> + echo "CONFIG_VHOST_USER_NET_TEST_$target_name=y" >> $config_host_mak
> + elif test -z "${VHOST_USER_NET_TEST_WARNED}"; then
> + echo "warning: vhost-user tests disabled" >&2
> + VHOST_USER_NET_TEST_WARNED="warned"
> + fi
> fi
> fi
> fi
> --
> 2.14.1
>
>
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2017-09-05 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 17:08 [Qemu-devel] [PATCH] vhost-user: disable broken test Philippe Mathieu-Daudé
2017-09-05 17:11 ` Peter Maydell
2017-09-05 17:17 ` Daniel P. Berrange [this message]
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=20170905171746.GI311@redhat.com \
--to=berrange@redhat.com \
--cc=f4bug@amsat.org \
--cc=peter.maydell@linaro.org \
--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 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).