Expected behavior when using CreateHardLinksForCopyLocalIfPossible

Cjewett commented 7 months ago

Our build output is getting so large that we are attempting to use CreateHardLinksForCopyLocalIfPossible. When we turn this setting on and attempt to run multiple test projects at the same time we run into an issue where Coverlet fails due to a System.IO.Exception. The exception is that the TestProject.dll cannot be accessed because it is being used by another process. That makes sense in the grand scheme of things, but I was wondering what the expected behavior was from the Coverlet maintainers. Is there a workaround?

github-actions[bot] commented 4 months ago

This issue is stale because it has been open for 3 months with no activity.

Bertk commented 4 weeks ago

Please add more details.

Configuration (please complete the following information): Please provide more information on your .NET configuration:

Which coverlet package and version was used?
Which version of .NET is the code running on?
What OS and version, and what distro if applicable?
What is the architecture (x64, x86, ARM, ARM64)?
Do you know whether it is specific to that configuration?

coverlet-coverage / coverlet

Expected behavior when using CreateHardLinksForCopyLocalIfPossible #1651