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.

Sign up for GitHub

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

Jump to bottom

[6.3.0] Don't rewind the build if invocation id stays the same #18670

Merged
merged 1 commit into from
Jun 14, 2023
Merged

[6.3.0] Don't rewind the build if invocation id stays the same #18670

merged 1 commit into from
Jun 14, 2023

Commits on Jun 14, 2023

  1. Don't rewind the build if invocation id stays the same 

    Invocation id (`BUILD_ID` in code) is expected to be different for each command. When retrying the build, we rely on Bazel generating a new invocation id for a new attempt. However, if flag `--invocation_id` is set, Bazel just uses the provided value instead of generating a new one. In this case, invocation id stays the same among multiple attempts which could cause issues like bazelbuild#18547.

This PR fixes that by not retrying the build if the invocation id is same to previous attempt. Also updated the doc to point this requirement out.

Closes bazelbuild#18591.

PiperOrigin-RevId: 539946840
Change-Id: I6ae85ea923b0fdbff97fe2e44e36995f0205f8a1
    @coeuvre
    coeuvre committed Jun 14, 2023
    Configuration menu
    Copy the full SHA
    7ea74d2 View commit details
    Browse the repository at this point in the history