On 09/03/2026 13.06, Peter Maydell wrote:
On Mon, 9 Mar 2026 at 12:03, Thomas Huth <[email protected]> wrote:
On 09/03/2026 12.55, 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
./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/
I think the functional tests log their output according to the current
working directory, so have a look at
$PWD/tests/functional/arm/test_emcraft_sf2.EmcraftSf2Machine.test_arm_emcraft_sf2/
instead of
$PWD/build/san/tests/functional/arm/test_emcraft_sf2.EmcraftSf2Machine.test_arm_emcraft_sf2/
No, there's nothing there (no directories created under
tests/functional/arm/). Also having build/test write to
the source directory rather than the build directory would be
surprising -- if it does that then we should definitely
alter the recommended command line in the docs to not
suggest running the 'run' script from the source directory.
Agreed, this sounds fishy. I can have a look at it after the softfreeze if
nobody else beats me to it.
Thomas
