On Mon, Mar 09, 2026 at 11:55:58AM +0000, Peter Maydell wrote: > The functional test documentation suggests running a single test > with the build/run script. But if you do this where do the logfiles go? > As you can see from this transcript, they don't seem to get written > into the place that a "make check-functional" run puts them: > > $ ls -l > build/san/tests/functional/arm/test_emcraft_sf2.EmcraftSf2Machine.test_arm_emcraft_sf2/ > total 16 > -rw-r--r-- 1 pm215 pm215 3084 Mar 9 10:51 base.log > -rw-r--r-- 1 pm215 pm215 825 Mar 9 10:51 console.log > -rw-r--r-- 1 pm215 pm215 235 Mar 9 10:54 default.log > drwxr-xr-x 3 pm215 pm215 4096 Mar 9 10:51 scratch > $ date > Mon Mar 9 11:20:13 GMT 2026 > $ time QEMU_TEST_QEMU_BINARY=./build/san/qemu-system-arm
BTW this is previously needed, but is now overkill wit the 'run' script. QEMU_TEST_QEMU_BINARY=qemu-system-arm is sufficient, as meson's devenv sets $PATH to include the locally built binary dirs first. > ./build/san/run tests/functional/arm/test_emcraft_sf2.py > TAP version 13 > ok 1 test_emcraft_sf2.EmcraftSf2Machine.test_arm_emcraft_sf2 > 1..1 > > real 3m24.394s > user 3m21.314s > sys 0m3.100s > $ ls -l > build/san/tests/functional/arm/test_emcraft_sf2.EmcraftSf2Machine.test_arm_emcraft_sf2/ > total 16 > -rw-r--r-- 1 pm215 pm215 3084 Mar 9 10:51 base.log > -rw-r--r-- 1 pm215 pm215 825 Mar 9 10:51 console.log > -rw-r--r-- 1 pm215 pm215 235 Mar 9 10:54 default.log > drwxr-xr-x 3 pm215 pm215 4096 Mar 9 10:51 scratch > > thanks > -- PMM > With regards, Daniel -- |: https://berrange.com ~~ https://hachyderm.io/@berrange :| |: https://libvirt.org ~~ https://entangle-photo.org :| |: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
