-
Notifications
You must be signed in to change notification settings - Fork 385
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
TestNodeFailingGracefulExitWithLowOnlineScore flaky #6401
Comments
The second example points at a data race:
|
That race appears to come from TestManyNodesGracefullyExiting, instead (see #6402). |
Change satellite/gracefulexit: de-flake TestNodeFailingGracefulExitWithLowOnlineScore mentions this issue. |
storjBuildBot
pushed a commit
that referenced
this issue
Nov 8, 2023
…lineScore I can't say with certainty yet what caused the two failures I know about, but I have one theory: the node continuing to check in during the test skewed the online score towards 1, and using the test default for GracefulExitDurationInDays meant there were fewer update periods than expected. At any rate, it is more correct to pause the graceful exit processing chore and the contact chore during the test, even if it doesn't end up solving the problem. Refs: #6401 Change-Id: I06d43d531e0b3344af13878c8d55213349fdcfa3
it seems like this fix has been deployed. I am going to close this issue @thepaul @shaupt131 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sample failures:
https://build.dev.storj.tools/blue/organizations/jenkins/storj-gerrit-verify/detail/storj-gerrit-verify/8974/tests
https://build.dev.storj.tools/blue/organizations/jenkins/storj-gerrit-verify/detail/storj-gerrit-verify/8975/tests
The text was updated successfully, but these errors were encountered: