fix: add retry handler for 429 or 503 - #132
Open
yamaceay wants to merge 1 commit into
Open
Conversation
alpkom
requested changes
Sep 9, 2026
alpkom
left a comment
alpkom
left a comment
Contributor
There was a problem hiding this comment.
Let's first see how often this fails, and try to identify the problem, before applying retries, Because this test takes relatively longer, and retrying might increase the total runtime of the integration tests significantly.
Feel free to create issue with logs from the failing test and involve the BLR colleagues to have a look, as well.
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.
Context
Fixes one flakiness in gen package integration tests
What this PR does and why it is needed
This PR adds retry handler for 429 or 503 status codes occurring in
TestMultipleExecutionFlow.Definition of Done