479b0cdb89
Both test-panic-abort-nocapture.rs and test-panic-abort.rs assert the stderr output of the test. On Fuchsia, if a test fails an assertion, this output will contain a line noting the process returned the code -1028 (ZX_TASK_RETCODE_EXCEPTION_KILL). But the asserted stderr output lacks this note. Presumably this is because other platforms implement -Cpanic=abort by killing the process instead of returned a status code.
33 lines
697 B
Plaintext
33 lines
697 B
Plaintext
|
|
running 6 tests
|
|
test benchmark ... ok
|
|
test it_exits ... FAILED
|
|
test it_fails ... FAILED
|
|
test it_panics - should panic ... ok
|
|
test it_works ... ok
|
|
test no_residual_environment ... ok
|
|
|
|
failures:
|
|
|
|
---- it_exits stdout ----
|
|
---- it_exits stderr ----
|
|
note: got unexpected return code 123
|
|
---- it_fails stdout ----
|
|
hello, world
|
|
testing123
|
|
---- it_fails stderr ----
|
|
testing321
|
|
thread 'main' panicked at $DIR/test-panic-abort.rs:40:5:
|
|
assertion `left == right` failed
|
|
left: 2
|
|
right: 5
|
|
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
|
|
|
|
|
|
failures:
|
|
it_exits
|
|
it_fails
|
|
|
|
test result: FAILED. 4 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out; finished in $TIME
|
|
|