-
Notifications
You must be signed in to change notification settings - Fork 382
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The process cannot access the file, because it is being used by another process" error during attempt to collect coverage #1471
Comments
Are you refering to #1155? The fix for this wasn't released yet, but it will be in the next release. You can try out the fix by consuming our nightly build (https://github.com/coverlet-coverage/coverlet/blob/master/Documentation/ConsumeNightlyBuild.md). |
Don't think he means that one, but this one: I'm facing this issue again when using coverlet.console v6.0.0 Just did some more testing with different versions of the tool: I don't have the issue using v3.1.x or v3.2.0, but I do with v6.0 With v6 I get this kind of exception: ---> System.IO.IOException: The process cannot access the file '(real path left out for nda reasons).pdb' because it is being used by another process. |
I just started encountering this same after installing the newly-released C# Dev Kit for VSCode. It seems the processes started by VSCode keep a handle open on the assemblies:
Once I close VSCode and run |
This issue is stale because it has been open for 3 months with no activity. |
This has been a problem for my team as we have minimum code coverage being applied to changed code as a policy in pull requests. This bug is preventing us from being able to complete pull requests. I have found that with this bug in 6.0.0, we get this error in the
|
This issue is stale because it has been open for 3 months with no activity. |
Issue should be closed because the related coverlet nuget package is not mentioned and comments for all packages are available. The new issue template for bugs should improve this. |
This issue is stale because it has been open for 3 months with no activity. |
I get the same error on one of my .NET 4.8 projects. I am using the coverlet console tool as part of an Azure Pipeline. Tool version is 6.0.2 The exit code from coverlet is 255, which is undocumented. Command:
Output: (...) BadImageFormatException during MetadataReaderProvider.FromPortablePdbStream in InstrumentationHelper.PortablePdbHasLocalSource, unable to check if module has got local source. |
We still have this issue on 6.0.0, 6.0.1 and 6.0.2. Version 3.2.0 still works fine. |
I can see previous issue being fixed in an unofficial version - did it ever make it to stable release?
The issue still exist with running test in parallel with vstest code coverage (XPlat code coverage)
The text was updated successfully, but these errors were encountered: