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

Investigate sensitivity to latency in multi instance tests #190

Merged
merged 1 commit into from
May 3, 2024

Conversation

masih
Copy link
Member

@masih masih commented May 3, 2024

Assert that when latency seed is changed the tests passes eventually. In this case, it looks like the change in latency results in few additional rounds for the test to pass; 21 to be precise.

Increase the max rounds to 30 in order to avoid intermittent errors during dev work that might change latency seeds.

Closes #189

Assert that when latency seed is changed the tests passes eventually. In
this case, it looks like the change in latency results in few additional
rounds for the test to pass; 21 to be precise.

Increase the max rounds to 30 in order to avoid intermittent errors
during dev work that might change latency seeds.

Closes #189
@masih masih requested a review from Kubuxu May 3, 2024 16:09
@masih masih enabled auto-merge May 3, 2024 16:11
@masih masih added this pull request to the merge queue May 3, 2024
@Kubuxu
Copy link
Contributor

Kubuxu commented May 3, 2024

I'm wondering if such behaviour also exists in other places but now it won't be a mystery (at least for me).

Merged via the queue into main with commit fea57b0 May 3, 2024
3 checks passed
@masih masih deleted the masih/invtgt-testfailure-rounds branch May 3, 2024 16:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

TestMultiAsyncAgreement is latency sensitive
2 participants