aspnet / Coherence

A build that verifies that all the packages form a consistent graph.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

The process cannot access the file '[...]\project.lock.json' because it is being used by another process.

Tratcher opened this issue · comments

The process cannot access the file 'D:\b\w\a6e561eeb4ed13a7\.packages\.tools\Microsoft.AspNetCore.Server.IISIntegration.Tools\1.0.0-preview2-21286\netcoreapp1.0\project.lock.json' because it is being used by another process.
C:\Users\asplab.REDMOND\AppData\Local\Microsoft\dotnet\dotnet.exe compile-csc @D:\b\w\a6e561eeb4ed13a7\Antiforgery\samples\AntiforgerySample\obj\Release\net451\dotnet-compile.rsp returned Exit Code 1

This error keeps causing Universe-Coherence to fail. Needs investigation.

I think the issue might be because dotnet build and dotnet restore don't share the same lock (and so we run into this).

I've forwarded this to Joel on nuget.

I'll turn off parallel builds until this is sorted. (Yaay for cleaner logs!)

[13:47:26][build-compile] The process cannot access the file 'D:\b\w\a6e561eeb4ed13a7\.packages\.tools\Microsoft.AspNetCore.Server.IISIntegration.Tools\1.0.0-preview2-21335\netcoreapp1.0\project.lock.json' because it is being used by another process.
[13:47:26][build-compile] C:\Users\asplab.REDMOND\AppData\Local\Microsoft\dotnet\dotnet.exe compile-csc @D:\b\w\a6e561eeb4ed13a7\CORS\test\WebSites\CorsMiddlewareWebSite\obj\Release\netcoreapp1.0\dotnet-compile.rsp returned Exit Code 1

Are we still seeing this?

Not since my last comment 5 days ago.

We haven't seen this since switching to building a repo at a time. It's twice as slow, but works. Closing this for now - we could reopen it if the CLI issue gets resolved.