Fix race in ClientMock.MockGet() #309
Merged
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.
What this PR does:
Recently we started seeing some compactor unit tests failing because of a race. The race is caused by the mocked
Get()function on thebucket.ClientMock. This PR fixes it.The problem is that testify (the testing lib we're also using for mocking) doesn't allow to specify a dynamic return value (eg. a function that's called each time to get the return value for the mocked function) and so to mock the returned
io.ReadCloserwe use the following trick:However, there's a race condition that could get
mockedGetto return the same reader twice and this cause some unit tests to fail from time to time.To fix it, I've used a smart solution outlined by @colega (thanks!).
Which issue(s) this PR fixes:
N/A
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX]