build pipelining fails

[khuey]

Problem

When running CARGO_BUILD_PIPELINING=true cargo build --all --tests on my project, I get

error: crate `<foo>` required to be available in rlib format, but was not found in this form

Unfortunately this project is not open source, so I'm not sure what else to report.

Notes

Output of cargo version: cargo 1.37.0-nightly (545f354 2019-05-23)

[nnethercote]

CC @alexcrichton

[alexcrichton]

Thanks for the report! Is it possible to share the project that generated this error?

[khuey]

Probably not. Is there a way to get debugging information out of cargo?

[alexcrichton]

If you're ok with it you can do a CARGO_LOG=trace cargo build ... and I can try to piece together what went wrong.

[khuey]

I can do that. The log is 67 MB. Can I email you a link to it?

[alexcrichton]

Sure!

[khuey]

Sent.

[alexcrichton]

Is this a build where RUSTC_WRAPPER is set in one way or another? The metadata file looks like it's getting produced at the exact same time as the output file which seems like there may be some caching somewhere. If so does this bug reproduce without the caching layer/wrapper?

[khuey]

We don't set that anywhere. I think the most interesting thing going on in our build is a linker script. We don't have anything like ccache involved.

[alexcrichton]

Ok thanks for the clarification, digging more I believe #7008 should at least fix one of the issues I saw (and was able to reproduce locally). Could you test that out and see if it fixes the issues you're seeing?

[khuey]

Unfortunately cargo master (and your PR) dies earlier with error: Unrecognized option: 'json-rendered' when CARGO_BUILD_PIPELINING=true, so I can't actually test it.

[alexcrichton]

To double check, you're doing the equivalent of rustup run nightly /path/to/cargo/target/debug/cargo build?