tree cceaa9159f68817134184c4a58c3f2024c0d46e8
parent df38c206022d89958cef89f3ce64ed9b22c8aa6b
author Googler <adgar@google.com> 1723140231 -0700
committer Copybara-Service <copybara-worker@google.com> 1723140338 -0700

Post `TestAttempt`/`TestResult` events when a test can be built but test-exec-config-inputs fail to build.

Usually, when a test target can be built, the `TestRunnerAction` will be
buildable, but this is not always the case. If the special `exec`-config inputs
fail to build, the test action may fail to build, which will only happen in the
`test` command. The build tool (and BEP) assume that if a test-type target is
buildable, and the command is `test`, then the corresponding
`TestAttempt`/`TestResult` events will eventually be posted.

This change ensures those events are posted with minimal, correct information indicating the test `FAILED_TO_BUILD`.

RELNOTES: BEP will include correct \`TestResult\` and \`TargetSummary\` events when special test inputs like \`$test_runtime\` fail to build.
PiperOrigin-RevId: 660904505
Change-Id: Ie44d558be5393ee910e6c4171ac295af2f34b182