Fix tests failing with cargo test but not with cargo nextest
#12061
+27
−9
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.
Related
What
The difference between those two is whether each test gets its own process. So it was clear that we're leaking state. Turns out it's about store subscribers which often rely on unique store ids for distinguishing concrete stores.
Solving this on the store subscriber level with the current arch is hard because the subscriber correctly accumulate data from all parallel running tests that do writes do stores with the exact same id