Closed rtfb closed 2 years ago
Actually, the failure is not consistent, sometimes there is some of the expected output, but not all of it:
--- testdata/want-output-u64.txt 2022-01-02 11:17:31.788702043 +0000
+++ out/test-output-u64.txt 2022-01-02 11:18:11.257047491 +0000
@@ -1,8 +1,5 @@
kinit: cpu 0000000000000000
Reading FDT...
-FDT ok
-bootargs: dry-run
-000000000000f10a
-cpu parked: 0000000000000001
-KKKK
+q
qemu-launcher: killing qemu due to timeout
+emu-system-riscv64: terminating on signal 15 from pid 4061 (python3)
make: *** [Makefile:94: out/test-output-u64.txt] Error 1
Error: Process completed with exit code 2.
The integration tests introduced in 10628f998f0cd67c2443e2af10513b1f0793e26f seem to be broken now.
qemu-launcher.py
fails to capture the stdout from qemu on the github test machines, while it works as expected on my dev box.The failure looks like this:
Qemu seems to produce none of the expected output, and prints an unexpected string
qemu-system-riscv64: terminating on signal 15 from pid 3995 (python3)
instead, which is interlaced withqemu-launcher: killing qemu due to timeout
, which is printf'ed directly from qemu-launcher.py.