arcade: Request failed "500 Internal Server Error"
Build
Build leg reported
Test: Blazor E2E tests on Linux / Run E2E tests
Pull Request
https://github.com/dotnet/aspnetcore/pull/44834
Action required for the engineering services team
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
{
"ErrorPattern" : "An unexpected error occurred: \"https://pkgs.dev.azure.com/dnceng/public/_packaging/.*: Request failed \\\\\"500 Internal Server Error\\\\\"",
"BuildRetry": true
}
Release Note Category
- Feature changes/additions
- Bug fixes
- Internal Infrastructure Improvements
Release Note Description
Additional information about the issue reported
No response
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 0 | 0 | 0 |
About this issue
- Original URL
- State: open
- Created 2 years ago
- Comments: 19 (19 by maintainers)
I brought this up in our ASP.NET Build teams channel. @wtgodbe is going to try adding retries to our
yarncommands. It’s a bit complicated because we use the Yarn.MSBuild package and that wraps commands.Our efforts to move to
npmaren’t really moving yet but are planned for this year (.NET 8 timeframe).Still reproing, IcM ticket is just claiming they don’t have telemetry for the problem still. Added repro from last night to the IcM and pinged the ticket.
Replied to requests in the IcM; I left step-by-step instructions how to get precise timestamps of what failed and such, hopefully they actually believe us now.