You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To triage this issue (First Responder / @dotnet/dnceng):
Open the failing build above and investigate
Add a comment explaining your findings
If this is an issue that is causing build breaks across multiple builds and would get benefit from being listed on the build analysis check, follow the next steps:
Add the label "Known Build Error"
Edit this issue and add an error string in the Json below that can help us match this issue with future build breaks. You should use the known issues documentation
{
"ErrorMessage" : "Response status code does not indicate success: 503 (Service Unavailable)",
"BuildRetry": false
}
Additional information about the issue reported
I'm seeing some restore failures accross repositories this morning. Opening a known issue to track the ones that happen in the public side. The message is a little broad as it will catch every 503 from Azure devops. If we do end up catching strays not related to feeds, I'll try to narrow it down a bit.
Build
https://dnceng.visualstudio.com/internal/_build/results?buildId=2017199
Build leg reported
All of them (in attempt 1)
Pull Request
No response
Action required for the engineering services team
To triage this issue (First Responder / @dotnet/dnceng):
If this is an issue that is causing build breaks across multiple builds and would get benefit from being listed on the build analysis check, follow the next steps:
Additional information about the issue reported
I'm seeing some restore failures accross repositories this morning. Opening a known issue to track the ones that happen in the public side. The message is a little broad as it will catch every 503 from Azure devops. If we do end up catching strays not related to feeds, I'll try to narrow it down a bit.
Report
Summary
The text was updated successfully, but these errors were encountered: