You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The docs currently recommend running tests with --test-threads=1, but this means that none of the tests can be run in parallel.
A simple solution without changing the design would be to take a global mutex whenever the first mock end-point is created on a thread, and release that mutex whenever the last mock end-point is dropped.
The text was updated successfully, but these errors were encountered:
it's not solving the core problem but it could allow tests not using mocks to perform in parallel, which is neat. would you be interested in making a PR?
The docs currently recommend running tests with
--test-threads=1
, but this means that none of the tests can be run in parallel.A simple solution without changing the design would be to take a global mutex whenever the first mock end-point is created on a thread, and release that mutex whenever the last mock end-point is dropped.
The text was updated successfully, but these errors were encountered: