Request failed "500 Internal Server Error"

Build

https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=93516

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:

1. Add the label “Known Build Error”
2. 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

[dougbu]

I brought this up in our ASP.NET Build teams channel. @wtgodbe is going to try adding retries to our yarn commands. It’s a bit complicated because we use the Yarn.MSBuild package and that wraps commands.

Our efforts to move to npm aren’t really moving yet but are planned for this year (.NET 8 timeframe).

[MattGal]

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.