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 unsynced objects in multicluster tests #621

Merged
merged 1 commit into from
Jan 21, 2025

Conversation

averevki
Copy link
Contributor

No description provided.

@averevki averevki added the bug Something isn't working label Jan 20, 2025
@averevki averevki force-pushed the fix-multicluster-tests branch from e2a2279 to 4265635 Compare January 20, 2025 19:36
@trepel
Copy link
Contributor

trepel commented Jan 21, 2025

@averevki lgtm. Do you think that it would be worth going through all the tests and update then to follow this approach (calling refresh() and then asserting the result)?

Copy link
Contributor

@trepel trepel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All tests in load_balanced dir passed for me.

@trepel trepel merged commit 9606102 into Kuadrant:main Jan 21, 2025
3 checks passed
@averevki
Copy link
Contributor Author

@averevki lgtm. Do you think that it would be worth going through all the tests and update then to follow this approach (calling refresh() and then asserting the result)?

I'm honestly still not sure why did this break in the first place. The issue only seems to occur when running tests inside a pod

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants