Open livarcocc opened 5 years ago
We are seeing this issue as well. Has anyone found a solution for the issue?
dotnet --info output:
.NET Core SDK (reflecting any global.json): Version: 2.1.302 Commit: 9048955601
Runtime Environment: OS Name: Windows OS Version: 6.3.9600 OS Platform: Windows RID: win81-x64 Base Path: C:\Program Files\dotnet\sdk\2.1.302\
Host (useful for support): Version: 2.1.2 Commit: 811c3ce6c0
.NET Core SDKs installed: 2.0.2 [C:\Program Files\dotnet\sdk] 2.1.2 [C:\Program Files\dotnet\sdk] 2.1.4 [C:\Program Files\dotnet\sdk] 2.1.101 [C:\Program Files\dotnet\sdk] 2.1.103 [C:\Program Files\dotnet\sdk] 2.1.201 [C:\Program Files\dotnet\sdk] 2.1.202 [C:\Program Files\dotnet\sdk] 2.1.302 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed: Microsoft.AspNetCore.All 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All] Microsoft.AspNetCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.NETCore.App 2.0.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 2.0.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 2.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 2.0.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 2.0.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 2.0.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
I've wiped the VM and recreated it, it started working again.
Since then I've replaced my single build agent with a pool of containerized build agents, it's been working well so far.
On Thu, Jan 24, 2019 at 7:38 PM Richard McGinnis notifications@github.com wrote:
We are seeing this issue as well. Has anyone found a solution for the issue?
dotnet --info output:
.NET Core SDK (reflecting any global.json): Version: 2.1.302 Commit: 9048955601
Runtime Environment: OS Name: Windows OS Version: 6.3.9600 OS Platform: Windows RID: win81-x64 Base Path: C:\Program Files\dotnet\sdk\2.1.302\
Host (useful for support): Version: 2.1.2 Commit: 811c3ce6c0
.NET Core SDKs installed: 2.0.2 [C:\Program Files\dotnet\sdk] 2.1.2 [C:\Program Files\dotnet\sdk] 2.1.4 [C:\Program Files\dotnet\sdk] 2.1.101 [C:\Program Files\dotnet\sdk] 2.1.103 [C:\Program Files\dotnet\sdk] 2.1.201 [C:\Program Files\dotnet\sdk] 2.1.202 [C:\Program Files\dotnet\sdk] 2.1.302 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed: Microsoft.AspNetCore.All 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All] Microsoft.AspNetCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.NETCore.App 2.0.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 2.0.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 2.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 2.0.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 2.0.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 2.0.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/NuGet/Home/issues/7644#issuecomment-457308461, or mute the thread https://github.com/notifications/unsubscribe-auth/ABS1AefoCylYFXCAoMfnxEs9M2bCY0mxks5vGf2ngaJpZM4ZWtlS .
Wiping the VM would be a hard option to sell with my employer. We have two separate build agents on separate servers. Each agent is running two pools and we see this issue across both agents in each of the pools at random intervals. Additionally, containerization would not be an option at this point.
In that case you're in a tough spot :/ I haven't been able to fix this in any different way
On Fri, Jan 25, 2019 at 4:29 PM Richard McGinnis notifications@github.com wrote:
Wiping the VM would be a hard option to sell with my employer. We have two separate build agents on separate servers. Each agent is running two pools and we see this issue across both agents in each of the pools at random intervals. Additionally, containerization would not be an option at this point.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/NuGet/Home/issues/7644#issuecomment-457610246, or mute the thread https://github.com/notifications/unsubscribe-auth/ABS1Ada3AqCMw23egUtEt_KM8vTseKtQks5vGyLpgaJpZM4ZWtlS .
From @mmisztal1980 on December 17, 2018 12:40
Steps to reproduce
Here's our build log obtained with dotnet restore -v diag https://gist.github.com/mmisztal1980/6ce8e016da620efbf0aa4693d4bc85b9
Expected behavior
We expect our build agent to complete this step (TFS dotnet task v2.*, targeting */.csproj (linked by default))
Actual behavior
The build appears to hang after iterating over the last project in the */.csproj. The last target appears to be _GenerateRestoreProjectPathWalk
Environment data
dotnet --info
output:octopus@build14:~/agent/_work/1/s/src$ dotnet --info .NET Core SDK (reflecting any global.json): Version: 2.1.500 Commit: b68b931422
Runtime Environment: OS Name: ubuntu OS Version: 18.04 OS Platform: Linux RID: ubuntu.18.04-x64 Base Path: /usr/share/dotnet/sdk/2.1.500/
Host (useful for support): Version: 2.1.6 Commit: 3f4f8eebd8
.NET Core SDKs installed: 2.1.500 [/usr/share/dotnet/sdk]
.NET Core runtimes installed: Microsoft.AspNetCore.All 2.1.6 [/usr/share/dotnet/shared/Microsoft.AspNetCore.All] Microsoft.AspNetCore.App 2.1.6 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App] Microsoft.NETCore.App 2.1.6 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
We'd apreciate some information how to diagnose this situation as we do not see any errors. This behavior has been observed in the master and feature branches of our repo.
Copied from original issue: dotnet/cli#10481