All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
	Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: qemu test-qga failure on mergebuild after VERSION file change: dependency issues??
Date: Thu, 16 Jul 2020 23:03:44 +0200	[thread overview]
Message-ID: <3c908ef9-ab28-665c-b963-ecfdf5af60a6@redhat.com> (raw)
In-Reply-To: <CAFEAcA9ejQjNMcChrGH4RMt9pERQpUx2titK527s+PQCmVUEkA@mail.gmail.com>

On 7/16/20 10:15 PM, Peter Maydell wrote:
> On Thu, 16 Jul 2020 at 20:52, Michael Roth <mdroth@linux.vnet.ibm.com> wrote:
>> But is it intermittent, environment-dependent? I'm trying to understand how to
>> replicate Peter's result since it seems like it would be straightforward
>> reproducer.
> 
> I blew away all my build trees and recreated them from
> scratch, and the issue went away. I'm suspicious that the
> complete lack of .d files was induced by a failed earlier
> pullreq attempt and left the build tree in a messed up state
> where it wouldn't notice that it needed to rebuild files.

If it happens again, can you try to revert aaa1b70a0b ("Makefile:
simplify MINIKCONF rules") on top of the tag you are testing, and
re-run the testing?



      reply	other threads:[~2020-07-16 21:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16 10:53 qemu test-qga failure on mergebuild after VERSION file change: dependency issues?? Peter Maydell
2020-07-16 12:11 ` Philippe Mathieu-Daudé
2020-07-16 17:55 ` Michael Roth
2020-07-16 17:59   ` Philippe Mathieu-Daudé
2020-07-16 19:52     ` Michael Roth
2020-07-16 20:06       ` Philippe Mathieu-Daudé
2020-07-16 20:15       ` Peter Maydell
2020-07-16 21:03         ` Philippe Mathieu-Daudé [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=3c908ef9-ab28-665c-b963-ecfdf5af60a6@redhat.com \
    --to=philmd@redhat.com \
    --cc=mdroth@linux.vnet.ibm.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 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.