Flaky test: InputDateInteractsWithEditContext_DateTimeLocalInput

[captainsafia]

Failing Test(s)

• Microsoft.AspNetCore.Components.E2ETest.Tests.FormsTest.InputDateInteractsWithEditContext_DateTimeLocalInput

Error Message

OpenQA.Selenium.BrowserAssertFailedException : Xunit.Sdk.EqualException: Assert.Equal() Failure\r\nExpected: modified valid\r\nActual:   modified invalid

Stacktrace

Details

OpenQA.Selenium.BrowserAssertFailedException : Xunit.Sdk.EqualException: Assert.Equal() Failure\r\nExpected: modified valid\r\nActual:   modified invalid\r\n   at Xunit.Assert.Equal[T](T expected, T actual, IEqualityComparer`1 comparer) in C:\\Dev\\xunit\\xunit\\src\\xunit.assert\\Asserts\\EqualityAsserts.cs:line 40\r\n   at Microsoft.AspNetCore.E2ETesting.WaitAssert.<>c__DisplayClass17_0.b__0() in /_/src/Shared/E2ETesting/WaitAssert.cs:line 83\r\n   at Microsoft.AspNetCore.E2ETesting.WaitAssert.<>c__DisplayClass18_0`1.b__0(IWebDriver _) in /_/src/Shared/E2ETesting/WaitAssert.cs:line 109\r\nScreen shot captured at 'D:\\workspace\\_work\\1\\s\\artifacts\\TestResults\\Release\\Microsoft.AspNetCore.Components.E2ETests\\49b0768a209a40d7ae2d1dc88b85f60a.png'\r\nEncountered browser errors\r\n[2021-07-30T04:54:04Z] [Severe] http://127.0.0.1:1080/_content/TestContentPackage/TestContentPackage.bundle.scp.css - Failed to load resource: the server responded with a status of 404 (Not Found)\r\n[2021-07-30T04:54:06Z] [Debug] http://127.0.0.1:1080/subdir/_framework/dotnet.6.0.0-rc.1.21374.7.js 0:129635 \"mono_wasm_runtime_ready\" \"fe00e07a-5519-4dfe-b35a-f867dbaf2e28\"\r\n[2021-07-30T04:54:16Z] [Warning] rendering 2 The specified value \"05/1992\" does not conform to the required format.  The format is \"yyyy-MM\" where yyyy is year in four or more digits, and MM is 01-12.Page content:\r\n\r\n    \r\n    \r\n    \r\n    \r\n    \r\n\r\n    \r\n    \r\n\r\n    \r\n    \r\n<title>Basic test app</title>\r\n\r\n\r\n    
\r\n    Select test:\r\n    Choose...\r\n        Add/remove child components\r\n        After-render interop component\r\n        Async event handlers\r\n        Auth cases\r\n        Cascading authentication state\r\n        bind cases\r\n        Cascading values\r\n        Component ref component\r\n        Concurrent rendering\r\n        Configuration\r\n        Content-editable\r\n        Counter\r\n        Counter using child component\r\n        Counter wrapped in parent\r\n        Culture Picker\r\n        data-* attribute rendering\r\n        Dispatching to sync context\r\n        Du
  CallStack
     at Microsoft.AspNetCore.E2ETesting.WaitAssert.WaitAssertCore[TResult](IWebDriver driver, Func`1 assertion, TimeSpan timeout) in /_/src/Shared/E2ETesting/WaitAssert.cs:line 129
   at Microsoft.AspNetCore.E2ETesting.WaitAssert.WaitAssertCore(IWebDriver driver, Action assertion, TimeSpan timeout) in /_/src/Shared/E2ETesting/WaitAssert.cs:line 84
   at Microsoft.AspNetCore.E2ETesting.WaitAssert.Equal[T](IWebDriver driver, T expected, Func`1 actual) in /_/src/Shared/E2ETesting/WaitAssert.cs:line 27
   at Microsoft.AspNetCore.Components.E2ETest.Tests.FormsTest.InputDateInteractsWithEditContext_DateTimeLocalInput() in /_/src/Components/test/E2ETest/Tests/FormsTest.cs:line 316
----- Inner Stack Trace -----
   at Microsoft.AspNetCore.E2ETesting.WaitAssert.<>c__DisplayClass17_0.b__0() in /_/src/Shared/E2ETesting/WaitAssert.cs:line 83
   at Microsoft.AspNetCore.E2ETesting.WaitAssert.<>c__DisplayClass18_0`1.b__0(IWebDriver _) in /_/src/Shared/E2ETesting/WaitAssert.cs:line 109

Logs

Details

Build

https://dev.azure.com/dnceng/public/_build/results?buildId=1267790&view=results

This test was green until yesterday. Perhaps something was merged that caused it to start failing?

Thanks for contacting us.

We're moving this issue to the Next sprint 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.