Consider all other exit codes besides 'test-success-exit-code' as failures

[Freax13]

• add test-no-reboot config key (defaults to true) to pass -no-reboot for test executables
• add a test that intentionally triggers a reboot/triple fault
• fix the check for exit-code 0

Closes #61

Edit (phil-opp): This is a breaking change.

[Freax13]

ci failing is probably not due to the changes:

error: failed to read `/usr/share/rust/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/src/libstd/Cargo.toml`

on an unrelated test.

Someone else also just posted this error on stackoverflow: https://stackoverflow.com/questions/63151602/rust-process-failed-with-exit-code-101-using-github-actions

[phil-opp]

Thanks for the pull request! I'm currently a bit busy, but I'll try to review this as soon as possible.

The CI changes are caused by a cargo bug in the latest nightly: rust-lang/cargo#8557. It was caused by the directory layout changes in rust-lang/rust#73265.

[phil-opp]

Looks good to me, thanks a lot!

[phil-opp]

Published as v0.10.0

[0xethsign]

Hey, I have the same error
thread 'test_middleware' panicked at 'requires the `rt` Tokio feature flag', /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.2.0/src/blocking.rs:18:9

The ci build is failing on github actions. What is the fix?