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

Fix sporadic failure in resolver migration unit test #1622

Merged
merged 2 commits into from
Aug 21, 2024

Conversation

tpantelis
Copy link
Contributor

The round-robin test may not see cluster1's IP yet which causes it to fail, instead just wait until the resolver eventually returns the IP.

The round-robin test may not see cluster1's IP yet which
causes it to fail, instead just wait until the resolver
eventually returns the IP.

Signed-off-by: Tom Pantelis <[email protected]>
@submariner-bot
Copy link
Contributor

🤖 Created branch: z_pr1622/tpantelis/fix_resolver_ut
🚀 Full E2E won't run until the "ready-to-test" label is applied. I will add it automatically once the PR has 2 approvals, or you can add it manually.

@submariner-bot submariner-bot added the ready-to-test When a PR is ready for full E2E testing label Aug 21, 2024
@skitt skitt enabled auto-merge (rebase) August 21, 2024 09:31
@skitt skitt merged commit 2efc187 into submariner-io:devel Aug 21, 2024
23 checks passed
@submariner-bot
Copy link
Contributor

🤖 Closed branches: [z_pr1622/tpantelis/fix_resolver_ut]

@dfarrell07
Copy link
Member

@tpantelis thinks this was related to a version bump that may not have happened on other branches. Not sure if we need to backport, will keep an eye out for the failure on other branches.

@tpantelis tpantelis deleted the fix_resolver_ut branch August 30, 2024 11:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-to-test When a PR is ready for full E2E testing
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

5 participants