Peter Maydell <[email protected]> writes:
> On Thu, 28 May 2020 at 16:18, Philippe Mathieu-Daudé <[email protected]> > 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
