-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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 in raft implementation #1180
Comments
@sanga We'll definitely get the race errors buttoned up. There was a lot of shuffling around of some pieces in |
Yeah, definitely something we will enable. As @benbjohnson mentioned, we're working through some of the new tests in master, and ensuring everything is solid. I'll make sure we get this turned on eventually. |
For kicks I tried this again this morning (against 59a953d), and you still have racy tests (or code)
|
Thanks @sanga -- yep, we know. We are fixing these as we work though it, though base features for the 0.9.0 release are obviously a high priority right now. We are holding off from enabling this on our CI system until the race count gets way down. PRs -- any fixes or suggested changes for this stuff -- are more than welcome in the meantime. |
This is definitely in prod code and unrelated to tests. I just reproed it by building with -race enabled and running the 3_shards test. Stack:
|
Go has a built in race detector (http://blog.golang.org/race-detector). Enabling it is as simple as: go test -v -race . ./messaging ./influxql in .travis.yml
And it actually finds some errors against current master 8049c34.
The text was updated successfully, but these errors were encountered: