Associated PR (only ensures other test jobs aren't cancelled, it doesn't fix the common stack overflow runtime failure).
Just documenting the CI test failures that I've seen in the logs (before they eventually disappear from age).
Feel free to close if this isn't a concern. I raise it because of the use of the matrix jobs, where presently the failure strategy will cancel all other test jobs when a failure is encountered, which you probably don't want (if you instead have a successful run of the x86_64 target separately that'd at least ensure everything appears to be working, without any target specific concerns that might be misleading due to QEMU usage?)
Failure with riscv64-linux (Feb 22 2026):
running 1 test
test system::tests::test_system ... ok
test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.04s
Running unittests src/lib.rs (target/riscv64gc-unknown-linux-gnu/debug/deps/c_scape-29b18e67a7f6e1c6)
running 6 tests
thread 'main' (10145) has overflowed its stack
fatal runtime error: stack overflow, aborting
error: test failed, to rerun pass `-p c-scape --lib`
Caused by:
process didn't exit successfully: `/opt/hostedtoolcache/qemu/bin/qemu-riscv64 -L /usr/riscv64-linux-gnu /home/runner/work/c-ward/c-ward/target/riscv64gc-unknown-linux-gnu/debug/deps/c_scape-29b18e67a7f6e1c6` (signal: 6, SIGABRT: process abort signal)
Error: Process completed with exit code 101.
Failure with aarch64-linux (Jan 21 2026):
running 1 test
test system::tests::test_system ... ok
test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.04s
Running unittests src/lib.rs (target/aarch64-unknown-linux-gnu/debug/deps/c_scape-e672b5e85faf8cbf)
running 6 tests
thread 'main' has overflowed its stack
fatal runtime error: stack overflow, aborting
qemu: uncaught target signal 6 (Aborted) - core dumped
error: test failed, to rerun pass `-p c-scape --lib`
Caused by:
process didn't exit successfully: `/opt/hostedtoolcache/qemu/bin/qemu-aarch64 -L /usr/aarch64-linux-gnu /home/runner/work/c-ward/c-ward/target/aarch64-unknown-linux-gnu/debug/deps/c_scape-e672b5e85faf8cbf` (signal: 6, SIGABRT: process abort signal)
Error: Process completed with exit code 101.
Associated PR (only ensures other test jobs aren't cancelled, it doesn't fix the common stack overflow runtime failure).
Just documenting the CI test failures that I've seen in the logs (before they eventually disappear from age).
aarch64andriscv64are the observed failures, and the only two that are configured to use QEMU.Feel free to close if this isn't a concern. I raise it because of the use of the matrix jobs, where presently the failure strategy will cancel all other test jobs when a failure is encountered, which you probably don't want (if you instead have a successful run of the
x86_64target separately that'd at least ensure everything appears to be working, without any target specific concerns that might be misleading due to QEMU usage?)Failure with
riscv64-linux(Feb 22 2026):Failure with
aarch64-linux(Jan 21 2026):