qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Kevin Wolf <kwolf@redhat.com>,
	qemu-devel@nongnu.org, stefanha@redhat.com
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [PATCH] qtest: Adding -display none to new tests
Date: Mon, 18 Nov 2013 17:09:12 +0100	[thread overview]
Message-ID: <528A3BA8.3030706@suse.de> (raw)
In-Reply-To: <1384545246-13556-1-git-send-email-kwolf@redhat.com>

Hi,

Am 15.11.2013 20:54, schrieb Kevin Wolf:
> Without it, you either get a window for a short time, or worse, test
> failures when 'make check' isn't run in an X session.
> 
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
>  tests/blockdev-test.c     | 2 +-
>  tests/qdev-monitor-test.c | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/tests/blockdev-test.c b/tests/blockdev-test.c
> index c940e00..fa49e09 100644
> --- a/tests/blockdev-test.c
> +++ b/tests/blockdev-test.c
> @@ -20,7 +20,7 @@ static void test_drive_add_empty(void)
>      const char *response_return;
>  
>      /* Start with an empty drive */
> -    qtest_start("-drive if=none,id=drive0");
> +    qtest_start("-display none -drive if=none,id=drive0");
[snip]

I've been wondering: Can't we just make qtest_start prepend -display
none always, so that we don't have to remember to repeatedly add it
everywhere?

Cheers,
Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

      parent reply	other threads:[~2013-11-18 16:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-15 19:54 [Qemu-devel] [PATCH] qtest: Adding -display none to new tests Kevin Wolf
2013-11-18 15:18 ` Stefan Hajnoczi
2013-11-18 15:31   ` Kevin Wolf
2013-11-18 16:09 ` Andreas Färber [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=528A3BA8.3030706@suse.de \
    --to=afaerber@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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).