search

dotnet / roslyn

The Roslyn .NET compiler provides C# and Visual Basic languages with rich code analysis APIs.
https://docs.microsoft.com/dotnet/csharp/roslyn-sdk/
MIT License
18.93k stars 4.02k forks source link

The process cannot access the file 'F:\vsagent\-containerSas\1\s\Binaries\Obj\Roslyn.Test.Utilities\Release\Roslyn.Test.Utilities.xml' because it is being used by another process. #31090

Open RikkiGibson opened 5 years ago

RikkiGibson commented 5 years ago

Causing build failures in CI. Appears to be a race around different targets trying to write the same output file. @jaredpar

2018-11-09T23:45:10.1478048Z Build FAILED.
2018-11-09T23:45:10.2008397Z 
2018-11-09T23:45:10.2015962Z CSC : error CS0016: Could not write to output file 'F:\vsagent\-containerSas\1\s\Binaries\Obj\Roslyn.Test.Utilities\Release\Roslyn.Test.Utilities.xml' -- 'The process cannot access the file 'F:\vsagent\-containerSas\1\s\Binaries\Obj\Roslyn.Test.Utilities\Release\Roslyn.Test.Utilities.xml' because it is being used by another process.' [F:\vsagent\-containerSas\1\s\src\Test\Utilities\Portable\Roslyn.Test.Utilities.csproj]
2018-11-09T23:45:10.2016262Z     0 Warning(s)
2018-11-09T23:45:10.2019189Z     1 Error(s)
2018-11-09T23:45:10.2019440Z 
2018-11-09T23:45:10.2020431Z Time Elapsed 00:09:29.36
2018-11-09T23:45:10.3427128Z Command failed to execute with exit code 1: C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin\msbuild.exe /p:TreatWarningsAsErrors=true /nologo /nodeReuse:false /p:Configuration=Release  /warnaserror /consoleloggerparameters:Verbosity=minimal;summary /m /bl:F:\vsagent\-containerSas\1\s\Binaries\Release\Logs\Roslyn.binlog /p:ContinuousIntegrationBuild=true /p:BootstrapBuildPath=F:\vsagent\-containerSas\1\s\Binaries\Bootstrap /t:Build /t:Pack /p:DeployExtension=false Roslyn.sln 
2018-11-09T23:45:10.3470142Z System.Management.Automation.RuntimeException: Command failed to execute with exit code 1: C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin\msbuild.exe /p:TreatWarningsAsErrors=true /nologo /nodeReuse:false /p:Configuration=Release  /warnaserror /consoleloggerparameters:Verbosity=minimal;summary /m /bl:F:\vsagent\-containerSas\1\s\Binaries\Release\Logs\Roslyn.binlog /p:ContinuousIntegrationBuild=true /p:BootstrapBuildPath=F:\vsagent\-containerSas\1\s\Binaries\Bootstrap /t:Build /t:Pack /p:DeployExtension=false Roslyn.sln 
2018-11-09T23:45:10.3497758Z at Exec-CommandCore, F:\vsagent\-containerSas\1\s\build\scripts\build-utils.ps1: line 66
2018-11-09T23:45:10.3498729Z at Exec-Console, F:\vsagent\-containerSas\1\s\build\scripts\build-utils.ps1: line 135
2018-11-09T23:45:10.3499636Z at Run-MSBuild, F:\vsagent\-containerSas\1\s\build\scripts\build.ps1: line 179
2018-11-09T23:45:10.3500498Z at Build-Artifacts, F:\vsagent\-containerSas\1\s\build\scripts\build.ps1: line 234
2018-11-09T23:45:10.3501258Z at <ScriptBlock>, F:\vsagent\-containerSas\1\s\build\scripts\build.ps1: line 582
jaredpar commented 5 years ago

Looks like we aren't properly dumping the XML file to the correct TF directory. Will fix build boss to detect this before fixing.

RikkiGibson commented 2 years ago

Is this issue still actionable? If not, we may want to close.