Skip to content
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

Expected behavior when using CreateHardLinksForCopyLocalIfPossible #1651

Open
Cjewett opened this issue Apr 19, 2024 · 2 comments
Open

Expected behavior when using CreateHardLinksForCopyLocalIfPossible #1651

Cjewett opened this issue Apr 19, 2024 · 2 comments
Labels
needs more info More details are needed stale untriaged To be investigated

Comments

@Cjewett
Copy link

Cjewett commented Apr 19, 2024

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?

Copy link

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

@github-actions github-actions bot added the stale label Jul 21, 2024
@Bertk Bertk added the needs more info More details are needed label Oct 25, 2024
@Bertk
Copy link
Collaborator

Bertk commented Oct 25, 2024

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?

@Bertk Bertk closed this as completed Oct 25, 2024
@Bertk Bertk reopened this Oct 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs more info More details are needed stale untriaged To be investigated
Projects
None yet
Development

No branches or pull requests

2 participants