[8.1.0] Forward exec_properties
to main test spawn's execution info
#25138
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This makes
exec_properties
such asno-remote-exec
effective for the main test spawn, where they previously only affected post-processing spawns such as test XML generation.Pros:
tags
) way to affect test execution using existing APICons:
exec_properties
such asOSFamily
andcontainer-image
, which shows up inaquery
and may increase memory usageexec_properties
end up in execution info appears to have been an unintentional side effect of adb56cc rather than a conscious design decisionCloses #24979.
PiperOrigin-RevId: 721088264
Change-Id: I7ce5c899ed6a647831f156f6b34c1f776655425c
Commit 357b091