Open radical opened 2 months ago
@MackinnonBuck Looks like there are 6 E2E tests failing consistently at the moment, including this one:
All of these failed on all four of the most recent main
builds, e.g., https://dev.azure.com/dnceng-public/public/_build/results?buildId=791847
Just from the build logs, it seems like they first started failing when this PR was merged: https://github.com/dotnet/aspnetcore/pull/57548. However it doesn't look likely that the PR was responsible because (1) the build checks passed on that PR before it was merged and (2) that PR only changes an unrelated test, not the product code. So it could be something unrelated like an update to Chrome.
I'm totally happy to look into this but don't want to duplicate your work if you already are doing so (since you're assigned here). Can you let me know whether it would be helpful for me to dig into this as well?
Actually because this is blocking all main
builds currently, I'll quarantine them: https://github.com/dotnet/aspnetcore/pull/57589
@MackinnonBuck If you track this down to an objective, fixable cause, please feel free to unquarantine them immediately.
Failing Test(s)
Microsoft.AspNetCore.Components.E2ETest.ServerExecutionTests.CircuitTests.ComponentLifecycleMethodThrowsExceptionTerminatesTheCircuit
Microsoft.AspNetCore.Components.E2ETest.ServerExecutionTests.CircuitTests.ComponentDisposeMethodThrowsExceptionTerminatesTheCircuit
Error Message
Stacktrace
Logs
Build