Failed tests lead to "could not execute process" errors

[huonw]

#[test]
pub fn foo() {
    fail!()
}

$ cargo test
   Compiling example v0.0.0 (...)
     Running ../target/test/example-8be7945be85d60d6

running 1 test
test foo ... FAILED

failures:

---- foo stdout ----
    task 'foo' failed at 'explicit failure', .../src/lib.rs:5



failures:
    foo

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured

task '<main>' failed at 'Some tests failed', /home/rustbuild/src/rust-buildbot/slave/nightly-linux/build/src/libtest/lib.rs:242
Could not execute process `.../target/test/example-8be7945be85d60d6` (status=101)

The last line is not true/relevant for cargo test. (cc #173)

[alexcrichton]

Hm yes, something like "Failed to execute" would probably be more relevant here.

[alexcrichton]

Or just omitting it entirely unless a signal was received like we do elsewhere.

[huonw]

Yeah, I think the test runner has enough output that cargo doesn't need to add any more (unless the test runner segfaults, etc.).