fixes #192 - guard access to reaper with a mutex #198
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hello @dvulpe! Thank you for your contribution! I am looking at why Travis failed and I will look at the code shortly |
|
thank you! |
gianarb
pushed a commit
that referenced
this pull request
Jun 9, 2020
master is red and the cause looks like a flaky test introduced by #198. I can't point the flakyness to code itself. And there are not race detected running `go test --race`. I spot that we are using a different image `localstack/localstack:latest` for that test. it is also very big 500mb. I changed it with nginx to keep consistency.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #192 by guarding access to shared reaper with a mutex making it thread safe.