We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
A test named peer_ping_failing is flapping in monitoringapi_internal_test: https://github.com/ObolNetwork/charon/runs/7615741168?check_suite_focus=true which is responsible to assert error obtained from ready function if peer is not able to connect to quorum number of peers. The problem lies here:
charon/app/monitoringapi_internal_test.go
Line 113 in e7e9998
which expects test to complete in 100ms. This test is non-deterministic since it depends on mutex to result in desired error.
Make this test deterministic by determining what is the ideal duration to check in require.Eventually function.
The text was updated successfully, but these errors were encountered:
app: fix flapy test in monitoringapi_internal_test (#934)
0711cf6
Fixes flapy test in monitoringapi_internal_test. category: test ticket: #886
dB2510
Successfully merging a pull request may close this issue.
Problem to be solved
A test named peer_ping_failing is flapping in monitoringapi_internal_test: https://github.com/ObolNetwork/charon/runs/7615741168?check_suite_focus=true which is responsible to assert error obtained from ready function if peer is not able to connect to quorum number of peers. The problem lies here:
charon/app/monitoringapi_internal_test.go
Line 113 in e7e9998
which expects test to complete in 100ms. This test is non-deterministic since it depends on mutex to result in desired error.
Proposed solution
Make this test deterministic by determining what is the ideal duration to check in require.Eventually function.
The text was updated successfully, but these errors were encountered: