-
Notifications
You must be signed in to change notification settings - Fork 491
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
Data Race: node catchpoint mode context R/W #3945
Labels
Comments
Commit which updates this code as well as adds the test which is showing the data race d868c91 |
I'm able to repro the failure individually without running all integ tests. It looks like it's not in the expect test, but in the go tests. Relevant log from test output:
|
Resolved in later version of #3920 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Subject of the issue
During the process of upgrading golang to 1.17.9 in go-algorand (#3919 ) we're seeing the data race detector reporting potential issues getting/setting the node's context.
You can see the issue https://app.circleci.com/pipelines/github/algorand/go-algorand/6177/workflows/c4decd97-e28b-4651-b897-a01c9bf708b6/jobs/105158/parallel-runs/1 in the CI run.
The write does acquire the
node.mu
lock, but the read (and potentially a few others as well) do not lock when reading the context.There does seem to be some diff between race detectors in go 1.16-1.17 so it's possible that the updated race detector is the delta that's causing this now.
Repro
I can repro this using
make integration
on Mac M1 using go1.17.9 changes mentioned in the PR linked above.The CI tests show this on amd64 however, so I expect it will show up on all archs.
The text was updated successfully, but these errors were encountered: