Increase retry attempts from 3 to 5#5
Merged
Conversation
Vertex AI rate limits (429) and transient timeouts (504) sometimes exhaust 3 retries during large evaluation runs. 5 retries with exponential backoff (4s, 4s, 8s, 16s, 32s) gives enough headroom.
emac-E
pushed a commit
that referenced
this pull request
Apr 10, 2026
LCORE-162: Setup all CI all linters/checkers
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
num_retriesfrom 3 to 5 for both LLM judge and API callsMotivation
During evaluation runs with heavy Vertex AI load, 429 rate limits and 504 gateway timeouts sometimes exhaust 3 retries, causing false errors on questions that would pass on the next attempt.