Quarantine CanRenderLargeComponentsWithServerRenderMode

[captainsafia]

Failing Test(s)

• Microsoft.AspNetCore.Components.E2ETests.ServerRenderingTests.RenderingTest.CanRenderLargeComponentsWithServerRenderMode

Error Message

OpenQA.Selenium.StaleElementReferenceException : stale element reference: stale element not found
  (Session info: chrome=115.0.5790.170); For documentation on this error, please visit: https://www.selenium.dev/documentation/webdriver/troubleshooting/errors#stale-element-reference-exception

Stacktrace

   at OpenQA.Selenium.WebDriver.UnpackAndThrowOnError(Response errorResponse, String commandToExecute)
   at OpenQA.Selenium.WebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters)
   at OpenQA.Selenium.WebDriver.InternalExecute(String driverCommandToExecute, Dictionary`2 parameters)
   at OpenQA.Selenium.WebElement.Execute(String commandToExecute, Dictionary`2 parameters)
   at OpenQA.Selenium.WebElement.get_Text()
   at Microsoft.AspNetCore.Components.E2ETests.ServerRenderingTests.RenderingTest.CanRenderLargeComponentsWithServerRenderMode() in /home/vsts/work/1/s/src/Components/test/E2ETest/ServerRenderingTests/RenderingTest.cs:line 34
   at InvokeStub_RenderingTest.CanRenderLargeComponentsWithServerRenderMode(Object, Object, IntPtr*)
   at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)

Logs

Build

• https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=368871

[halter73]

Quarantined by #49976

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.

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.