Quarantine CanRenderComponentWithPersistedState(suppressEnhancedNavigation: False, renderMode: typeof(Microsoft.AspNetCore.Components.Web.InteractiveAutoRenderMode), streaming: "AutoStreaming"/null)

[SteveSandersonMS]

Failing Test(s)

• Microsoft.AspNetCore.Components.E2ETests.Tests.StatePersistenceTest.CanRenderComponentWithPersistedState

... but only the following variants:

[InlineData(true, typeof(InteractiveAutoRenderMode), (string)null)]
[InlineData(false, typeof(InteractiveAutoRenderMode), (string)null)]
[InlineData(false, typeof(InteractiveAutoRenderMode), "AutoStreaming")]

We need to verify this is not a product bug before 8.0 ships, so putting it in the 8.0 milestone.

Error Message

Xunit.Sdk.EqualException: Assert.Equal() Failure
Expected: Interactive runtime: server
Actual:   Interactive runtime: wasm

Stacktrace

   at Microsoft.AspNetCore.E2ETesting.WaitAssert.WaitAssertCore[TResult](IWebDriver driver, Func`1 assertion, TimeSpan timeout) in /home/vsts/work/1/s/src/Shared/E2ETesting/WaitAssert.cs:line 129
   at Microsoft.AspNetCore.E2ETesting.WaitAssert.WaitAssertCore(IWebDriver driver, Action assertion, TimeSpan timeout) in /home/vsts/work/1/s/src/Shared/E2ETesting/WaitAssert.cs:line 83
   at Microsoft.AspNetCore.E2ETesting.WaitAssert.Equal[T](IWebDriver driver, T expected, Func`1 actual) in /home/vsts/work/1/s/src/Shared/E2ETesting/WaitAssert.cs:line 27
   at Microsoft.AspNetCore.Components.E2ETests.Tests.StatePersistenceTest.AssertPageState(String mode, String renderMode, Boolean interactive, Boolean stateFound, String stateValue, String streamingId, Boolean streamingCompleted, String interactiveRuntime) in /home/vsts/work/1/s/src/Components/test/E2ETest/Tests/StatePersistenceTest.cs:line 225
   at Microsoft.AspNetCore.Components.E2ETests.Tests.StatePersistenceTest.RenderComponentsWithPersistentStateAndValidate(Boolean suppresEnhancedNavigation, String mode, Type renderMode, String streaming, String interactiveRuntime, String stateValue) in /home/vsts/work/1/s/src/Components/test/E2ETest/Tests/StatePersistenceTest.cs:line 197
   at Microsoft.AspNetCore.Components.E2ETests.Tests.StatePersistenceTest.CanRenderComponentWithPersistedState(Boolean suppressEnhancedNavigation, Type renderMode, String streaming) in /home/vsts/work/1/s/src/Components/test/E2ETest/Tests/StatePersistenceTest.cs:line 101
   at InvokeStub_StatePersistenceTest.CanRenderComponentWithPersistedState(Object, Span`1)
   at System.Reflection.MethodBaseInvoker.InvokeWithFewArgs(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
----- Inner Stack Trace -----
   at Microsoft.AspNetCore.E2ETesting.WaitAssert.<>c__DisplayClass18_0`1.<WaitAssertCore>b__0(IWebDriver _) in /home/vsts/work/1/s/src/Shared/E2ETesting/WaitAssert.cs:line 101

Logs

Build

https://dev.azure.com/dnceng-public/public/_build/results?buildId=411184
https://dev.azure.com/dnceng-public/public/_build/results?buildId=411665
https://dev.azure.com/dnceng-public/public/_build/results?buildId=457395

[SteveSandersonMS]

Note that since these are [InlineData] cases, they can't be quarantined in the normal way. So instead I've commented out those lines. They will not get unquarantined automatically. The person resolving this issue needs to uncomment them to bring them back.

[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]

To learn more about what this message means, what to expect next, and how this issue will be handled you can read our Triage Process document.
We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. Because it's not immediately obvious what is causing this behavior, we would like to keep this around to collect more feedback, which can later help us determine how to handle this. 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 work.

[amcasey]

Saw a new failure in Microsoft.AspNetCore.Components.E2ETests.Tests.StatePersistenceTest.CanRenderComponentWithPersistedState(suppressEnhancedNavigation: True, renderMode: typeof(Microsoft.AspNetCore.Components.Web.InteractiveAutoRenderMode), streaming: "AutoStreaming")​

OpenQA.Selenium.BrowserAssertFailedException : Xunit.Sdk.EqualException: Assert.Equal() Failure
Expected: Interactive runtime: wasm
Actual:   Interactive runtime: server

[BrennanConroy]

And Microsoft.AspNetCore.Components.E2ETests.Tests.StatePersistenceTest.CanRenderComponentWithPersistedState(suppressEnhancedNavigation: True, renderMode: typeof(Microsoft.AspNetCore.Components.Web.InteractiveAutoRenderMode), streaming: null) in https://dev.azure.com/dnceng-public/public/_build/results?buildId=482738&view=ms.vss-test-web.build-test-results-tab&runId=11110162&resultId=101127&paneView=debug

[ghost]

To learn more about what this message means, what to expect next, and how this issue will be handled you can read our Triage Process document.
We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. Because it's not immediately obvious what is causing this behavior, we would like to keep this around to collect more feedback, which can later help us determine how to handle this. 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 work.