Include implicit output targets from cc_binary in cc_test

[jtilahun]

Description of the feature request:

The cc_binary rule adds implicit output targets for each explicit output target, as documented here. In particular, for an explicit target name defined using the cc_binary rule, the implicit target name.stripped outputs a stripped version of the binary. However, the cc_test rule does not add any such implicit output targets.

What underlying problem are you trying to solve with this feature?

In order to run a test on an auxiliary target, there are two steps to perform:

1. Build the test binary on the host machine using the appropriate toolchain. This can be accomplished by running bazel build on the test target with the appropriate options.
2. Upload the test binary from the host machine to the target machine and run the test binary on the target machine.

The upload step takes longer the larger the binary is. Unstripped binaries can be significantly larger than stripped binaries. So uploading a stripped binary is one way to make the upload step faster. The cc_binary rule enables this through the implicit name.stripped target. However, the cc_test rule does not.

Which operating system are you running Bazel on?

Linux Ubuntu 20.04

What is the output of bazel info release?

release 4.2.1

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

No response

What's the output of git remote get-url origin; git rev-parse master; git rev-parse HEAD ?

No response

Have you found anything relevant by searching the web?

No response

Any other information, logs, or outputs that you want to share?

No response

[jtilahun]

Given that #18275 has been approved and merged, are there other actions left to do here?

There aren't changes in the documentation here. Are there any follow-ups or things that need to be updated or refreshed?

[github-actions]

Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 1+ years. It will be closed in the next 90 days unless any other activity occurs. If you think this issue is still relevant and should stay open, please post any comment here and the issue will no longer be marked as stale.