qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Brad Smith" <brad@comstyle.com>, "Warner Losh" <imp@bsdimp.com>,
	"Kyle Evans" <kevans@freebsd.org>,
	"Ed Maste" <emaste@freebsd.org>, "Li-Wen Hsu" <lwhsu@freebsd.org>
Subject: Re: [PATCH] tests/qtest: Disable the spice test of readconfig-test on FreeBSD
Date: Fri, 28 Apr 2023 16:19:29 +0100	[thread overview]
Message-ID: <ZEvkAUOlPlt1ij0C@redhat.com> (raw)
In-Reply-To: <20230428151351.1365822-1-thuth@redhat.com>

On Fri, Apr 28, 2023 at 05:13:51PM +0200, Thomas Huth wrote:
> The spice test is currently hanging on FreeBSD. It likely was
> never working before, since in the past, our configure script
> was failing to detect this feature due to a bug in the spice
> package there (it just got enabled recently by the commit
> https://cgit.freebsd.org/ports/commit/?id=cf16b1c9063351325f0 ).
> To get the CI working again, let's disable the failing test for
> now until someone has enough spare time to debug and fix the real
> underlying problem.
> 
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
>  tests/qtest/readconfig-test.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)

Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>


though could you file a gitlab bug report and link the bug report
in a comment at the #ifdef the code change, and in the commit
message.

> 
> diff --git a/tests/qtest/readconfig-test.c b/tests/qtest/readconfig-test.c
> index 2160603880..918d45684b 100644
> --- a/tests/qtest/readconfig-test.c
> +++ b/tests/qtest/readconfig-test.c
> @@ -86,8 +86,8 @@ static void test_x86_memdev(void)
>      qtest_quit(qts);
>  }
>  
> -
> -#ifdef CONFIG_SPICE
> +/* FIXME: The test is currently broken on FreeBSD */
> +#if defined(CONFIG_SPICE) && !defined(__FreeBSD__)
>  static void test_spice_resp(QObject *res)
>  {
>      Visitor *v;
> @@ -209,7 +209,7 @@ int main(int argc, char *argv[])
>          qtest_add_func("readconfig/x86/memdev", test_x86_memdev);
>          qtest_add_func("readconfig/x86/ich9-ehci-uhci", test_docs_config_ich9);
>      }
> -#ifdef CONFIG_SPICE
> +#if defined(CONFIG_SPICE) && !defined(__FreeBSD__)
>      qtest_add_func("readconfig/spice", test_spice);
>  #endif
>  
> -- 
> 2.31.1
> 

With 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 :|



      parent reply	other threads:[~2023-04-28 15:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-28 15:13 [PATCH] tests/qtest: Disable the spice test of readconfig-test on FreeBSD Thomas Huth
2023-04-28 15:19 ` Marc-André Lureau
2023-04-28 15:19 ` Daniel P. Berrangé [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=ZEvkAUOlPlt1ij0C@redhat.com \
    --to=berrange@redhat.com \
    --cc=brad@comstyle.com \
    --cc=emaste@freebsd.org \
    --cc=imp@bsdimp.com \
    --cc=kevans@freebsd.org \
    --cc=lwhsu@freebsd.org \
    --cc=marcandre.lureau@redhat.com \
    --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).