microsoft / microsoft/MSBuildCache
Second build cannot start on the machine due to local cache locks
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 64
- Forks
- 24
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 2
Description
It can be a problem on developers using two IDEs on different enlistment. The local cache has per benefit, but it is not bigger enough to make it essential. Is there a way it can fall back to skip local cache when it is locked by another build session.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the local-cache lock handling and the build-session path used by concurrent IDE builds; define and test behavior when another session holds the lock, with the cache skipped so the second build can proceed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100