OK after asking around, I'm not sure who to bug, but from the logs it definitely doesn't look like the nuget functionality dotnet is using is being re-tried. @rrelyea on the Nuget team may be able to comment about how to do restore with some kind of build in retry?
@dotnet-mc-bot commented on Thu Aug 30 2018
Opened on behalf of @spshant @RussKeldorph the build is failing due to Filesystem error. Can you please take a look.
Warnings: 2 Status Message: failed
Build : 3.0 - 20180830.01 (Product Build) Failing configurations:
@MattGal commented on Fri Aug 31 2018
@spshant I'm not sure you meant to create this issue in core-eng, but I'll take a peek anyways :)
@MattGal commented on Fri Aug 31 2018
The problem is fairly obvious, just hidden a couple steps up due to CoreCLR not failing when things fail:
E:\A_work\147\s\bin\Product\Windows_NT.arm.Checked\IL doesn't exist because you hit a Nuget 503 from the storage account:
@MattGal commented on Fri Aug 31 2018
The "busy server" here is unfortunately myget and not our storage account, I'll ask around for guidance for this.
@MattGal commented on Fri Aug 31 2018
OK after asking around, I'm not sure who to bug, but from the logs it definitely doesn't look like the nuget functionality dotnet is using is being re-tried. @rrelyea on the Nuget team may be able to comment about how to do restore with some kind of build in retry?