Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[8.1.0] Forward exec_properties to main test spawn's execution info #25138

Merged
merged 1 commit into from
Jan 29, 2025

Conversation

bazel-io
Copy link
Member

This makes exec_properties such as no-remote-exec effective for the main test spawn, where they previously only affected post-processing spawns such as test XML generation.

Pros:

  • relatively simple (and more precise than tags) way to affect test execution using existing API
  • provides consistency between test spawns
  • provides consistency between test spawns and spawns produced by Starlark actions

Cons:

  • similar to Starlark actions, execution info is "polluted" with exec_properties such as OSFamily and container-image, which shows up in aquery and may increase memory usage
  • the fact that exec_properties end up in execution info appears to have been an unintentional side effect of adb56cc rather than a conscious design decision
  • provides functionality may be better addressed by Execution Platform Scoped Spawn Strategies

Closes #24979.

PiperOrigin-RevId: 721088264
Change-Id: I7ce5c899ed6a647831f156f6b34c1f776655425c

Commit 357b091

This makes `exec_properties` such as `no-remote-exec` effective for the main test spawn, where they previously only affected post-processing spawns such as test XML generation.

Pros:
* relatively simple (and more precise than `tags`) way to affect test execution using existing API
* provides consistency between test spawns
* provides consistency between test spawns and spawns produced by Starlark actions

Cons:
* similar to Starlark actions, execution info is "polluted" with `exec_properties` such as `OSFamily` and `container-image`, which shows up in `aquery` and may increase memory usage
* the fact that `exec_properties` end up in execution info appears to have been an unintentional side effect of bazelbuild@adb56cc rather than a conscious design decision
* provides functionality may be better addressed by [Execution Platform Scoped Spawn Strategies](https://github.com/bazelbuild/proposals/blob/main/designs/2023-06-04-exec-platform-scoped-spawn-strategies.md)

Closes bazelbuild#24979.

PiperOrigin-RevId: 721088264
Change-Id: I7ce5c899ed6a647831f156f6b34c1f776655425c
@bazel-io bazel-io added team-Configurability platforms, toolchains, cquery, select(), config transitions team-Remote-Exec Issues and PRs for the Execution (Remote) team labels Jan 29, 2025
@bazel-io bazel-io requested a review from a team as a code owner January 29, 2025 21:29
@bazel-io bazel-io added the awaiting-review PR is awaiting review from an assigned reviewer label Jan 29, 2025
@bazel-io bazel-io requested a review from katre January 29, 2025 21:29
@katre katre enabled auto-merge January 29, 2025 21:31
@katre katre added this pull request to the merge queue Jan 29, 2025
Merged via the queue into bazelbuild:release-8.1.0 with commit ad2d568 Jan 29, 2025
46 checks passed
@github-actions github-actions bot removed the awaiting-review PR is awaiting review from an assigned reviewer label Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team-Configurability platforms, toolchains, cquery, select(), config transitions team-Remote-Exec Issues and PRs for the Execution (Remote) team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants