Skip to content

Core: Increase wait time of flaky test - #12714

Merged
nastra merged 1 commit into
apache:mainfrom
manuzhang:fix-flaky-test-2
Apr 28, 2025
Merged

nastra merged 1 commit into
apache:mainfrom
manuzhang:fix-flaky-test-2

Conversation

@manuzhang

Copy link
Copy Markdown
Member

No description provided.

@danielcweeks

danielcweeks commented Apr 4, 2025 •

Copy link
Copy Markdown
Contributor

@manuzhang an alternative to this is just to remove the Awaitility and let the concurrency just run naturally. This reduces the overall test time from ~60s to ~10s for me. I'm not sure this gating is really helping with validation of concurrency.

Thoughts @nastra?

@manuzhang

Copy link
Copy Markdown
Member Author

an alternative to this is just to remove the Awaitility and let the concurrency just run naturally.

@danielcweeks You don't wait for it to finish?

@manuzhang

Copy link
Copy Markdown
Member Author

@nastra can you take a look? I'm seeing this flaky test quite often now.

Awaitility.await()
.pollInterval(Duration.ofMillis(10))
.atMost(Duration.ofSeconds(10))
.atMost(Duration.ofSeconds(60))

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I'm not convinced that this will actually help but I'm ok merging this and trying it out. If that doesn't help, then we should consider refactoring the test to avoid flakiness

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants