Components.E2ETests don't block the build, but having tests that nearly always fail isn't really helpful and it can make it look like there are issues with PRs to the unitiated.
The tests I'm about to skip are:
Microsoft.AspNetCore.Components.E2ETest.ServerExecutionTests.ServerTransportsTest.ErrorIfWebSocketsConnectionIsRejectedMicrosoft.AspNetCore.Components.E2ETest.ServerExecutionTests.ServerTransportsTest.ErrorIfClientAttemptsWebSocketsWithServerOnLongPollingMicrosoft.AspNetCore.Components.E2ETest.ServerExecutionTests.ServerTransportsTest.DefaultTransportsWorksWithWebSocketsMicrosoft.AspNetCore.Components.E2ETest.ServerExecutionTests.ServerTransportsTest.ErrorIfClientAttemptsLongPollingWithServerOnWebSockets
It looks like these weren't touched by #35414.
@SteveSandersonMS
Components.E2ETests don't block the build, but having tests that nearly always fail isn't really helpful and it can make it look like there are issues with PRs to the unitiated.
The tests I'm about to skip are:
Microsoft.AspNetCore.Components.E2ETest.ServerExecutionTests.ServerTransportsTest.ErrorIfWebSocketsConnectionIsRejectedMicrosoft.AspNetCore.Components.E2ETest.ServerExecutionTests.ServerTransportsTest.ErrorIfClientAttemptsWebSocketsWithServerOnLongPollingMicrosoft.AspNetCore.Components.E2ETest.ServerExecutionTests.ServerTransportsTest.DefaultTransportsWorksWithWebSocketsMicrosoft.AspNetCore.Components.E2ETest.ServerExecutionTests.ServerTransportsTest.ErrorIfClientAttemptsLongPollingWithServerOnWebSocketsIt looks like these weren't touched by #35414.
@SteveSandersonMS