On Tue, Feb 17, 2026 at 12:52 PM Thomas Huth <[email protected]> wrote: > > On 16/02/2026 22.29, John Snow wrote: > > With the qemu.qmp and qemu.machine dependencies now installed by default > > at configure time and additional dependencies required by functional > > testing installed on demand, we do not need the explicit "check-venv" > > target. > > > > ...However, to facilitate running VM tests without running configure, we > > move some of the former logic into tests/vm/Makefile.include to create a > > new venv (vm-venv) on-demand when running VM tests from the source tree. > > > > Signed-off-by: John Snow <[email protected]> > > --- > > tests/Makefile.include | 22 ++-------------------- > > tests/vm/Makefile.include | 18 ++++++++++++++---- > > 2 files changed, 16 insertions(+), 24 deletions(-) > > Maybe consider adding "vm-venv" to the .gitignore file now?
I wasn't sure. Leaving it un-ignored at least calls attention to it if you want to delete it. Can you run "make clean" on a bare repo you haven't run configure on? If so, I could have make clean delete that venv and then also add it to the ignore files. I could also just instantiate the venv in ~/.cache/qemu/vm-venv alongside the other VM temporary files.... thoughts? > > Anyway, > Tested-by: Thomas Huth <[email protected]> >
