Try running 'bazel cquery //...' before target-determinator #4531
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.
Trying to improve robustness against failures such as here:
Which is coming from the target-determinator invocation:
My thought is that the
bazel cquery
should trigger equivalent downloads (equally though, I'd thought thebazel mod deps
would do that, so I don't want to give the impression of confidence).It's harder to inject this into the target-determinator command line, since we'd need something that retries by default.