weird run-tests.py with VIRT_RV32 port

[yf13]

I am still learning micropython with QEMU VIRT_RV32 port.

As a learning task. I built firmware.elf for BOARD VIRT_RV32 on Ubuntu 22.004 with cmake and riscv64-unknown-elf toolchain v10.2. I can access the REPL interface after booting it like qemu-system-riscv32 -M virt -nographic -semihosting -bios none -kernel firmware.elf.

I then tried run-tests.py with it and got a failure case:

$ ./run-tests -t -t execpty:"qemu-system-riscv32 -bios none -machine virt -nographic -monitor null -semihosting  -serial pty -kernel /tmp/aaa/firmware.elf"
773 tests performed (23404 individual testcases)
772 tests passed
148 tests skipped:
1 tests failed: asmarith
$ cat results/inlineasm_rv32_asmarith.py.out
0xfe
Traceback (most recent call last):
  File "<stdin>", line 39, in <module>
TypeError: can't convert str to int

However, when I tried the inlineasm/rv32/asmarith.py with REPL, I can't see that exception. but I noticed that the result from f2() is different from expectation. Mine is 0x88 but expected is 0x111.

I am wondering if there are hints for further investigations?

Update-1

I can get expected result from the cmake artifact like below:

$ cd ~/Projects/micropython
$ tools/pyboard.py tests/inlineasm/rv32/asmarith.py -d "execpty:qemu-system-riscv32 -bios none -machine virt -nographic -monitor null -semihosting  -serial pty -kernel /tmp/aaa/firmware.elf"
0xfe
0x111
1
0
0
0
1
0
0
0
0
1
0
1

Maybe the cause is within run-tests.py?

Update-2

Release build passed with run-tests.py, while debug build doesn't yet. Here I attached both debug and release firmware ELFs for review. The debug image works with pyboard.py but not with run-tests.py for the asmarith test.