Problem
Cargo testsuite fails when built with the rustc-1.33.0-src tarball with vendor = true enabled. Though I haven't confirmed it yet, the issue may also exist if cargo itself is built with vendored crates.
Specifically, the test suite appears to expect error messages like [..]Cargo.toml but with vendoring enabled, messages will look like </path/to/vendor/dir>/Cargo.toml
Steps
- Download the
rustc-1.33.0-src tarball
- Edit
config.toml and set the vendor = true flag
./x.py test src/tools/cargo
Possible Solution(s)
- Update the test suite to understand if vendoring is currently enabled and react accordingly
- Have the test instance of
cargo ignore any .cargo config directories in the parent hierarchy
Notes
Problem
Cargo testsuite fails when built with the
rustc-1.33.0-srctarball withvendor = trueenabled. Though I haven't confirmed it yet, the issue may also exist ifcargoitself is built with vendored crates.Specifically, the test suite appears to expect error messages like
[..]Cargo.tomlbut with vendoring enabled, messages will look like</path/to/vendor/dir>/Cargo.tomlSteps
rustc-1.33.0-srctarballconfig.tomland set thevendor = trueflag./x.py test src/tools/cargoPossible Solution(s)
cargoignore any.cargoconfig directories in the parent hierarchyNotes