wasm32_final_outputs test fails when Cargo 0.23 is compiled from rustc source tarball

[saintdev]

When running cargo test from the src/tools/cargo directory in the rustc 1.22.1 source tarball, the wasm32_final_outputs test fails. It seems that the test is finding the rustc Cargo.toml instead of the cargo Cargo.toml and it fails because the test directory is not part of the workspace.

test wasm32_final_outputs ... FAILED
test wrong_message_format_option ... ok
test verbose_release_build ... ok
test verbose_release_build_deps ... ok

failures:

---- wasm32_final_outputs stdout ----
	thread 'wasm32_final_outputs' panicked at 'Can't create workspace: CargoError(Msg("current package believes it\'s in a workspace when it\'s not:\ncurrent:   /home/build/YPKG/root/cargo/build/rustc-1.22.1-src/src/target/cit/t118/foo/Cargo.toml\nworkspace: /home/build/YPKG/root/cargo/build/rustc-1.22.1-src/src/Cargo.toml\n\nthis may be fixable by adding `target/cit/t118/foo` to the `workspace.members` array of the manifest located at: /home/build/YPKG/root/cargo/build/rustc-1.22.1-src/src/Cargo.toml"), State { next_error: None, backtrace: None })', src/libcore/result.rs:906:4
note: Run with `RUST_BACKTRACE=1` for a backtrace.


failures:
    wasm32_final_outputs

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

error: test failed, to rerun pass '--test build'

[alexcrichton]

Thanks for the report! I think this is more of a bug with rust-lang/rust integration rather than Cargo, though, so I'm going to close this. Can you reopen on rust-lang/rust if you'd like to see it fixed?