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.

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

FLAKEY_TEST: Add retry to outbound request for ProxyLifecycleShutdown… #3999

Merged
merged 3 commits into from
May 17, 2024

Conversation

NiniOak
Copy link
Collaborator

@NiniOak NiniOak commented May 16, 2024

Changes proposed in this PR

  • Test fails intermittently in CI (for some reason it only fails in cloud environment not kind clusters) see example here
  • Add retry to outbound API calls to improve chance of success.
    • if error occures, log the error and mark the current attempt as failed, trigger a retry.
    • If error does not exist, check if the output contains the specific error message. If the condition fails, log the error message and trigger a retry.

How I've tested this PR

CI should pass

How I expect reviewers to test this PR

CI should pass

Checklist

@NiniOak NiniOak added backport/1.1.x Backport to release/1.1.x branch pr/no-changelog PR does not need a corresponding .changelog entry backport/1.2.x This release branch is no longer active. backport/1.3.x This release branch is no longer active. backport/1.4.x labels May 16, 2024
@NiniOak NiniOak requested review from a team, nathancoleman and jm96441n and removed request for a team May 16, 2024 17:45
@NiniOak NiniOak force-pushed the fix_flakey_ProxyLifecycleShutdownTest branch from de1aa38 to b7ecab4 Compare May 16, 2024 23:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/1.1.x Backport to release/1.1.x branch backport/1.2.x This release branch is no longer active. backport/1.3.x This release branch is no longer active. backport/1.4.x pr/no-changelog PR does not need a corresponding .changelog entry
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants