-
Notifications
You must be signed in to change notification settings - Fork 161
Starting multiple inmemory instanced does not work #481
Comments
I suspect this is the safety feature of having a lock file in the repository to guard against accessing it from two different processes. In fact, before this feature was added, there were a number of issues of me accidentially using the single repository and getting bad results, and wasting time. You could for example use a temporary directory for this the purpose of testing. |
How would a temporary directory help if everything is in memory anyways? |
No, it should not help, nor should it be needed. If this was the case, it'd be a bug. Could you share how are you hitting this issue with in-memory repository? Initialization code, and/or other details would help, or those in comparison to the tests in the repository. |
Yeah, sure: https://git.beyermatthi.as/distrox/tree/src/client.rs?h=ipfs-backend#n127 It is just very simple stuff as I'm still playing with ideas... I am doing nothing more than just |
On line 130:
Please try replacing |
Argh. Thanks! |
Describe the bug
In my codebase:
Expected behavior
Tests run in parallel
Additional context
Running multiple in-memory nodes should be possible, as rust tests run in parallel.
The text was updated successfully, but these errors were encountered: