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

[7.4.0] Replace "checking cached actions" message when no action is running. #23357

Merged

Conversation

bazel-io
Copy link
Member

While we delay the execution phase progress until we execution real actions (see unknown commit), with Skymeld we could still see the following scenario:

  • Bazel completes the analysis for the first top-level target
  • Bazel starts execution for the first top-level target, still analyzing other top-level targets
  • Bazel completes execution for the first top-level target, still running analysis for other top-level targets

Prior to this CL, we would have reported something like [42 / 42] checking cached actions until we continue with execution (after the next top-level target finishes analysis). Now, we do report [42 / 42] no actions running.

RELNOTES: Improve progress message in case there are no actions in flight, and display explicitly "no actions running" in that case.
PiperOrigin-RevId: 661205481
Change-Id: Ieaf77090ecf3d4979330fcd8229a92afc98c7557

Commit b215cb8

While we delay the execution phase progress until we execution real actions (see unknown commit), with Skymeld we could still see the following scenario:
- Bazel completes the analysis for the first top-level target
- Bazel starts execution for the first top-level target, still analyzing other top-level targets
- Bazel completes execution for the first top-level target, still running analysis for other top-level targets

Prior to this CL, we would have reported something like `[42 / 42] checking cached actions` until we continue with execution (after the next top-level target finishes analysis). Now, we do report `[42 / 42] no actions running`.

RELNOTES: Improve progress message in case there are no actions in flight, and display explicitly "no actions running" in that case.
PiperOrigin-RevId: 661205481
Change-Id: Ieaf77090ecf3d4979330fcd8229a92afc98c7557
@bazel-io bazel-io requested a review from a team as a code owner August 19, 2024 22:44
@bazel-io bazel-io added team-Remote-Exec Issues and PRs for the Execution (Remote) team awaiting-review PR is awaiting review from an assigned reviewer labels Aug 19, 2024
@iancha1992 iancha1992 enabled auto-merge (squash) August 19, 2024 22:46
@iancha1992 iancha1992 added this pull request to the merge queue Aug 21, 2024
Merged via the queue into bazelbuild:release-7.4.0 with commit a9a66ae Aug 21, 2024
52 checks passed
@github-actions github-actions bot removed the awaiting-review PR is awaiting review from an assigned reviewer label Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team-Remote-Exec Issues and PRs for the Execution (Remote) team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants