Fix race condition of Tesla.Mock.mock_global/1 #456
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.
Problem:
Intermittent test failures when using
Tesla.Mock.mock_global/1
Current implementation:
agent_set/1
is not atomic, and there's no guarantee pid returned byProcess.whereis/1
will be alive when makingAgent.update/2
call. That's becauseAgent
process is linked to the test process, but theexit(:shutdown)
signal is asynchronous, thus the same process can "leak" between test cases in certain edge cases.Proposed implementation:
Instead of using plain
Agent.start_link/2
useExUnit.Callbacks.start_supervised!/1
, that puts theTesla.Mock
agent under the test supervision tree and guarantees the process is terminated synchronously, thus prevents the leak between test cases.