-
Notifications
You must be signed in to change notification settings - Fork 15
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
Fix racy tests and enable race detection on travis #14
Comments
@stoewer do you still need any help with this? I can give it a shot if you wish :) |
Hi @marcosinger, that would be great! |
@stoewer I'm having a bad time to configure Nakadi server on macOS.. after googling while it's running but I'm getting a duplicated key error running Go tests.. I can post a screenshot here if it helps, but do you have any clue on top your head about this issue?! |
The integration tests and the tests examples create event types before the tests and remove them afterwards. However, if tests are interrupted the created event types or subscriptions might still exist on Nakadi. I guess this is the most likely explanation for the duplicated keys. The solution is just to stop Nakadi You can check if the event type still exists with the GET /event-types endpoint. I hope this helps. |
@marcosinger Are you still working on this one? |
@stoewer I'm still getting a bunch of errors from Nakadi server and the tests aren't passing :( To not block it you could get this issue back to you, if you wish. |
@marcosinger The problem with Nakadi's docker compose setup is known but apparently not solved right now. There is a pull request that tries to solve it, but it still has errors. Since I would really like to turn race detection on, I'd take this one over. If this is OK? |
@stoewer go for it! |
When tests are run with
go test -race
several race conditions are detected (see #7). Those race conditions must be fixed.To avoid racy tests in the future the
-race
flag should be enabled for all tests in the.travis.yaml
file.The text was updated successfully, but these errors were encountered: