From: "Alex Bennée" <alex.bennee@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Gerd Hoffmann" <kraxel@redhat.com>
Subject: Re: [PULL 00/12] testing and plugin fixes
Date: Thu, 28 May 2020 18:19:31 +0100 [thread overview]
Message-ID: <877dww3rks.fsf@linaro.org> (raw)
In-Reply-To: <CAFEAcA-EZ_c01599j+NJH1Vd0aJ4cQzwPYynx=rBZP7x_3h3jg@mail.gmail.com>
Peter Maydell <peter.maydell@linaro.org> writes:
> On Thu, 28 May 2020 at 16:18, Philippe Mathieu-Daudé <philmd@redhat.com> wrote:
>>
>> +Gerd
>>
>> On 5/28/20 5:09 PM, Peter Maydell wrote:
>> > Yes. I see them also now on the next pullreq I'm trying to
>> > process. How do I get back to an environment that doesn't
>> > produce all these warnings?
>>
>> Maybe building back NetBSD 8.1?
>
> Did that change not itself trigger the VM to be rebuilt ?
> If not, can we make it so that updates to the images always
> do trigger rebuilds, so that we can catch new warnings
> that they introduce at the time rather than later?
$(IMAGES_DIR)/%.img: $(SRC_PATH)/tests/vm/% \
So netbsdb.img should have been rebuilt when tests/vm/netbsd was
touched. However maybe the packages have been updated upstream since? As
we also have:
$(SRC_PATH)/tests/vm/basevm.py \
$(SRC_PATH)/tests/vm/Makefile.include
I suspect the genisoimage change to basevm triggered a re-build grabbing
the latest packages.
--
Alex Bennée
next prev parent reply other threads:[~2020-05-28 17:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 14:54 [PULL 00/12] testing and plugin fixes Alex Bennée
2020-05-27 14:54 ` [PULL 01/12] configure: add alternate binary for genisoimage Alex Bennée
2020-05-27 14:54 ` [PULL 02/12] tests/vm: pass --genisoimage to basevm script Alex Bennée
2020-05-27 14:54 ` [PULL 03/12] travis.yml: Use clang++ in the Clang tests Alex Bennée
2020-05-27 14:54 ` [PULL 04/12] tests/tcg: fix invocation of the memory record/replay tests Alex Bennée
2020-05-27 14:54 ` [PULL 05/12] tests/fp: enable extf80_le_quite tests Alex Bennée
2020-05-27 14:54 ` [PULL 06/12] tests/fp: split and audit the conversion tests Alex Bennée
2020-05-27 14:54 ` [PULL 07/12] tests/tcg: better detect confused gdb which can't connect Alex Bennée
2020-05-27 14:54 ` [PULL 08/12] tests/docker: add debian11 base image Alex Bennée
2020-05-27 14:54 ` [PULL 09/12] tests/docker: use a gcc-10 based image for arm64 tests Alex Bennée
2020-05-27 14:54 ` [PULL 10/12] cpus-common: ensure auto-assigned cpu_indexes don't clash Alex Bennée
2020-05-27 14:54 ` [PULL 11/12] linux-user: properly "unrealize" vCPU object Alex Bennée
2020-05-27 14:54 ` [PULL 12/12] tests/tcg: add new threadcount test Alex Bennée
2020-05-28 13:54 ` [PULL 00/12] testing and plugin fixes Peter Maydell
2020-05-28 14:16 ` Alex Bennée
2020-05-28 14:57 ` Alex Bennée
2020-05-28 15:09 ` Peter Maydell
2020-05-28 15:18 ` Philippe Mathieu-Daudé
2020-05-28 15:20 ` Peter Maydell
2020-05-28 15:26 ` Philippe Mathieu-Daudé
2020-05-28 16:07 ` Peter Maydell
2020-05-28 17:19 ` Alex Bennée [this message]
2020-05-28 15:38 ` Gerd Hoffmann
2020-05-29 18:25 ` Peter Maydell
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=877dww3rks.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--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).