Doug Bunting
Doug Bunting
> Does the EFCore repo uses build analysis? Known issues tracking is part of build analysis No. /cc @bricelam and @ajcvickers because I don't remember why they didn't opt in...
Would that issue have picked up the efcore-ci failure given it occurred in a rolling build (where build analysis isn't relevant) for a repo where build analysis isn't enabled anyhow❔
In any case, the `ErrorMessage` above means this issue will capture a superset of those tracked in #11737. I'll reopen the other one just because `500` and `503` aren't the...
Oh, ignore my last comment. You were talking about the `dotnet-public-npm` failures. Right @MattGal❔
Side note: The Known Build Errors infrastructure is tilted pretty far toward PR failures. It's far too manual (AFAICT) to use for rolling build failures and the https://msit.powerbi.com/groups/de8c4cb8-b06d-4af8-8609-3182bb4bdc7c/reports/f0702582-7c04-47ca-a145-6ac37fd25813/ReportSectioncb62e8e5baebca8883e1?experience=power-bi doesn't seem...
@aaubry, this one is important in something I'd like to change in .NET build infrastructure. if you have a minute to suggest an approach, I'm happy to put some time...
/backport to release/7.0
We had a window in which we weren't testing templates using the latest ASP.NET runtime and my PR this weekend fixed that issue. If it explains the remaining flakiness, we're...
This test also has a duplicate name and is in a `class` with a duplicate name. See - https://github.com/dotnet/aspnetcore/blob/d66bbde41ee3c9d6c8f05746035c0cd50b0f1a93/src/ProjectTemplates/test/BlazorWasmTemplateTest.cs#L84 - https://github.com/dotnet/aspnetcore/blob/d66bbde41ee3c9d6c8f05746035c0cd50b0f1a93/src/ProjectTemplates/BlazorTemplates.Tests/BlazorWasmTemplateTest.cs#L241