From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Yang Hongyang <hongyang.yang@easystack.cn>,
QEMU Developers <qemu-devel@nongnu.org>,
Gerd Hoffmann <kraxel@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] qemu-ga: do not run qga test when guest agent disabled
Date: Tue, 19 Apr 2016 17:25:41 -0500 [thread overview]
Message-ID: <20160419222541.11723.23534@loki> (raw)
In-Reply-To: <CAFEAcA8z9HQf_pRTAeVQhFQy8CQ3gRwj4-unB9fbnyqHXGVzfg@mail.gmail.com>
Quoting Peter Maydell (2016-04-19 17:08:03)
> On 19 April 2016 at 23:01, Michael Roth <mdroth@linux.vnet.ibm.com> wrote:
> > Quoting Yang Hongyang (2016-04-19 02:39:13)
> >> When configure with --disable-guest-agent, make check will fail with:
> >> ERROR:tests/test-qga.c:74:fixture_setup: assertion failed (error == NULL):
> >> Failed to execute child process "/home/xx/qemu/qemu-ga" (No such file or
> >> directory) (g-exec-error-quark, 8)
> >> make: *** [check-tests/test-qga] Error 1
> >>
> >> This check was commented out by bab47d9a75a. I think that was by
> >> mistake, because the commit message of that commit didn't mention
> >> this change.
> >>
> >> Signed-off-by: Yang Hongyang <hongyang.yang@easystack.cn>
> >> Cc: Gerd Hoffmann <kraxel@redhat.com>
> >> Cc: Michael S. Tsirkin <mst@redhat.com>
> >> Cc: Michael Roth <mdroth@linux.vnet.ibm.com>
> >> Cc: Paolo Bonzini <pbonzini@redhat.com>
> >
> > Thanks, applied to qga tree:
> > https://github.com/mdroth/qemu/commits/qga
> >
> > As much as I'd like to get this fixed for 2.6, the net effect, thanks to
> > the inadvertant commenting out of qga test case in bab47d9a75a, is that
> > the qemu-ga unit test currently gets skipped during make check. Given
> > RC3 is going to be tagged soon, and afaik is the last RC, I'm not
> > sure I would consider this enough of a blocker to send a last-minute
> > pull.
> >
> > Peter: if you think there's still a window to get this in let me know
> > and I'll send the pull immediately. But for now I'll queue this for
> > 2.7 and for stable.
>
> Well, I'm not planning to tag RC3 til Thursday, so you have time
> in that sense. Whether it's worth putting into RC3 I leave to
> your judgement (it sounds like the only effect of not having it
> is "there's a test case we could be running that we don't run" ?)
Yes. Although the patch fixes a more serious build/make check issue
with --disable-guest-agent, the inadvertant commenting in bab47d9a75a
(which was probably to work around that bug) masks the build failures
by unconditionally disabling the test.
Since disabling the unit test is a late regression, I think it's
probably worthwhile to try to fix as long as it isn't holding up
the release. Will send a pull shortly.
>
> thanks
> -- PMM
>
prev parent reply other threads:[~2016-04-19 22:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 7:39 [Qemu-devel] [PATCH] qemu-ga: do not run qga test when guest agent disabled Yang Hongyang
2016-04-19 7:52 ` Yang Hongyang
2016-04-19 22:01 ` Michael Roth
2016-04-19 22:08 ` Peter Maydell
2016-04-19 22:25 ` Michael Roth [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=20160419222541.11723.23534@loki \
--to=mdroth@linux.vnet.ibm.com \
--cc=hongyang.yang@easystack.cn \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--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).