Quarantine ClosingTheBrowserWindow_GracefullyDisconnects_TheCurrentCircuit

[dougbu]

Failing Test(s)

Microsoft.AspNetCore.Components.E2ETest.ServerExecutionTests.ClosingTheBrowserWindow_GracefullyDisconnects_TheCurrentCircuit()

This test has been passing only about 55% of the time over the last two weeks.

Error Message

Error message
Assert.True() Failure
Expected: True
Actual:   False

Stacktrace

   at Microsoft.AspNetCore.Components.E2ETest.ServerExecutionTests.CircuitGracefulTerminationTests.ClosingTheBrowserWindow_GracefullyDisconnects_TheCurrentCircuit() in /home/vsts/work/1/s/src/Components/test/E2ETest/ServerExecutionTests/CircuitGracefulTerminationTests.cs:line 71
--- End of stack trace from previous location ---

Logs

Microsoft.AspNetCore.Components.E2ETests.zip

Build

For example, build #20220923.29

[dougbu]

/cc @dotnet/aspnet-blazor-eng

[dougbu]

Note #44186 will quarantine this test in the release/7.0 branch.

[MackinnonBuck]

I've found that when running locally with headless mode disabled, this test succeeds consistently. It appears that the unload event is flaky in headless mode specifically, causing the _blazor/disconnect request to never get sent, resulting in the test failure.

There is also the question of how much value this test is really adding - especially in non-desktop scenarios, the unload event is highly unreliable, so graceful termination of the circuit on tab/window close is more of an exception than the rule.

[MackinnonBuck]

We should address this after we implement #39409.

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.