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
EphemeralMongo also uses .NET Process class to start mongod.exe from your project output directory.
If I run the integration test end to end for the first time, it works perfectly. But if force the execution to end in the middle of the test (Shift + F5), the mongod.exe is left running. Then if I make any change in the test code and try to run the test again, the IDE can't copy the mongod.exe file to the output directory, so I can't run the tests.
This is happening because the mongod process is still running.
The text was updated successfully, but these errors were encountered:
Hi @marcosdeassis, I don't think it is related to Windows Defender Firewall, it's really just that the process is still running and at compilation time MSBuild tries to overwrite the file.
It might be because I used CopyToOutputDirectory = Always instead of PreserveNewest. I'll make some tests later to see if this behavior is the root cause of your issue.
In the meantime, I just released 1.1.0 which contains an experimental flag MongoRunnerOptions.KillMongoProcessesWhenCurrentProcessExits that makes sure any mongo process gets killed if the running process (in your case, the IDE test host) is prematurely killed. It only works on Windows and modern .NET (.NET Core and later).
Hi,
I'm facing an issue that might be related to the following behavior mentioned in the issue: "Windows Defender Firewall" want to block communication of testhost.exe
If I run the integration test end to end for the first time, it works perfectly. But if force the execution to end in the middle of the test (Shift + F5), the
mongod.exe
is left running. Then if I make any change in the test code and try to run the test again, the IDE can't copy themongod.exe
file to the output directory, so I can't run the tests.This is happening because the
mongod
process is still running.The text was updated successfully, but these errors were encountered: