[ci_runner] Save last used startup options to apply to cleanup commands #8653
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.
During remote runner cleanup, we run a bazel command to check that the bazel lock isn't still held by the server, which would indicate some corruption on the machine.
However, if a customer runs a bazel command with startup options, because we don't apply these same startup options during our cleanup command, the bazel server ends up getting killed and restarted.
To work around this before we can figure out a different solution (tracked here), save the startup options from the last executed bazel command so we can apply them during cleanup