rustdoc --test ignores --target

[asomers]

rustdoc's --target option works when building documentation, but it seems to be ignored when running tests. At the very least, using both options together should result in an error. Ideally, rustdoc would invoke a cross compiler in this case. It can be useful, for example, to execute doc tests in 32-bit mode on a 64-bit host.

To reproduce: Running rustdoc --target=itanium-multics-gnu --test <more valid options> should result in an error, but instead the doc tests run fine.

[dianpopa]

I have an inquiry regarding running documentation tests when using a target different than the default one.
My project is intended to run with target x86_64-unknown-linux-musl which is specified in .cargo/config. When I do a simple cargo test the Doc-tests are not run. However, If I remove it from there, I am able to see the Doc-tests being run. I am compiling on an x86 machine. Also, If I keep the musl target and I specifically run cargo test like cargo test --target x86_64-unknown-linux-gnu the Doc-tests are successfully run. I am guessing I stumbled upon #4471 which seems to be the expected behavior. However, to me this is not exactly cross-compilation as I am on an x86 host and trying to obtain a musl enabled binary for the same type of architecture (i.e. x86).
What is your opinion on this? Is this a bug?

[ehuss]

Closing in favor of the tracking issues #64245 and rust-lang/cargo#7040.