ServerErrorBoundaryTest.CanHandleMultipleAsyncErrorsFromDescendants

[Tratcher]

Error Message

OpenQA.Selenium.BrowserAssertFailedException : Xunit.Sdk.CollectionException: Assert.Collection() Failure
Collection: [Element (id = fd2a908c-e98e-4e57-ad44-fa8dfc22e92b), Element (id = 25f83cb8-3012-4ed2-b522-c4b67e4cb6d9), Element (id = 4a5a59e9-f1ba-4295-a465-d9f4e4a43a9f), Element (id = 4b8d67c5-674f-4d45-8ff6-7e56347e34b3), Element (id = 8b569678-25b1-45c1-b3ad-664b0c48bb36), ...]
Expected item count: 3
Actual item count:   6
   at Xunit.Assert.Collection[T](IEnumerable1 collection, Action1[] elementInspectors) in C:\Dev\xunit\xunit\src\xunit.assert\Asserts\CollectionAsserts.cs:line 63
   at Microsoft.AspNetCore.E2ETesting.WaitAssert.<>c__DisplayClass17_0.<WaitAssertCore>b__0() in /_/src/Shared/E2ETesting/WaitAssert.cs:line 83
   at Microsoft.AspNetCore.E2ETesting.WaitAssert.<>c__DisplayClass18_0`1.<WaitAssertCore>b__0(IWebDriver ) in //src/Shared/E2ETesting/WaitAssert.cs:line 109
Screen shot captured at 'D:\workspace\_work\1\s\artifacts\TestResults\Release\Microsoft.AspNetCore.Components.E2ETests\484409a1e64947278e2626f199f63414.png'
Encountered browser errors
[2021-06-11T23:42:27Z] [Info] http://127.0.0.1:1052/subdir/_framework/blazor.server.js 0:32028 "[2021-06-11T23:42:27.029Z] Information: Normalizing '_blazor' to 'http://127.0.0.1:1052/subdir/_blazor'."
[2021-06-11T23:42:27Z] [Info] http://127.0.0.1:1052/subdir 45:16 "Blazor server-side"
[2021-06-11T23:42:27Z] [Info] http://127.0.0.1:1052/subdir/_framework/blazor.server.js 0:32028 "[2021-06-11T23:42:27.213Z] Information: WebSocket connected to ws://127.0.0.1:1052/subdir/_blazor?id=P3qSq7yN3pFUqBOm6vfsyg."
[2021-06-11T23:42:29Z] [Severe] http://127.0.0.1:1052/subdir/_framework/blazor.server.js 0:105740 "[2021-06-11T23:42:28.838Z] Error: There was an unhandled exception on the current circuit, so this circuit will be terminated. For more details turn on detailed exceptions by setting 'DetailedErrors: true' in 'appSettings.Development.json' or set 'CircuitOptions.DetailedErrors'. "
[2021-06-11T23:42:29Z] [Info] http://127.0.0.1:1052/subdir/_framework/blazor.server.js 0:32028 "[2021-06-11T23:42:28.839Z] Information: Connection disconnected."
[2021-06-11T23:42:29Z] [Info] http://127.0.0.1:1052/subdir/_framework/blazor.server.js 0:32028 "[2021-06-11T23:42:29.350Z] Information: Normalizing '_blazor' to 'http://127.0.0.1:1052/subdir/_blazor'."
[2021-06-11T23:42:29Z] [Info] http://127.0.0.1:1052/subdir 45:16 "Blazor server-side"
[2021-06-11T23:42:29Z] [Info] http://127.0.0.1:1052/subdir/_framework/blazor.server.js 0:32028 "[2021-06-11T23:42:29.358Z] Information: WebSocket connected to ws://127.0.0.1:1052/subdir/_blazor?id=pShvcQ21xWCHp2V5Fza7Ng."
[2021-06-11T23:42:29Z] [Info] http://127.0.0.1:1052/subdir/_framework/blazor.server.js 0:32028 "[2021-06-11T23:42:29.806Z] Information: Normalizing '_blazor' to 'http://127.0.0.1:1052/subdir/_blazor'."
[2021-06-11T23:42:29Z] [Info] http://127.0.0.1:1052/subdir 45:16 "Blazor server-side"
[2021-06-11T23:42:29Z] [Info] http://127.0.0.1:1052/subdir/_framework/blazor.server.js 0:32028 "[2021-06-11T23:42:29.818Z] Information: WebSocket connected to ws://127.0.0.1:1052/subdir/_blazor?id=CrJL3qbrBewa6J4BuM8pXw."
[2021-06-11T23:42:31Z] [Info] http://127.0.0.1:1052/subdir/_framework/blazor.server.js 0:32028 "[2021-06-11T23:42:31.219Z] Information: Normalizing '_blazor' to 'http://127.0.0.1:1052/subdir/_blazor'."
[2021-06-11T23:42:31Z] [Info] http://127.0.0.1:1052/subdir 45:16 "Blazor server-side"
[2021-06-11T23:42:31Z] [Info] http://127.0.0.1:1052/subdir/_framework/blazor.server.js 0:32028 "[2021-06-11T23:42:31.223Z] Information: WebSocket connected to ws://127.0.0.1:1052/subdir/_blazor?id=orgzhnSwtu_msvBGp0DNZA."
[2021-06-11T23:42:33Z] [Info] http://127.0.0.1:1052/subdir/_framework/blazor.server.js 0:32028 "[2021-06-11T23:42:33.267Z] Information: Normalizing '_blazor' to 'http://127.0.0.1:1052/subdir/_blazor'."
[2021-06-1

Stacktrace

   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.Collection[T](IWebDriver driver, Func`1 actualValues, Action`1[] elementInspectors) in /_/src/Shared/E2ETesting/WaitAssert.cs:line 45
   at Microsoft.AspNetCore.Components.E2ETest.Tests.ErrorBoundaryTest.CanHandleMultipleAsyncErrorsFromDescendants() in /_/src/Components/test/E2ETest/Tests/ErrorBoundaryTest.cs:line 154
----- Inner Stack Trace -----
   at Microsoft.AspNetCore.E2ETesting.WaitAssert.<>c__DisplayClass17_0.<WaitAssertCore>b__0() in /_/src/Shared/E2ETesting/WaitAssert.cs:line 83
   at Microsoft.AspNetCore.E2ETesting.WaitAssert.<>c__DisplayClass18_0`1.<WaitAssertCore>b__0(IWebDriver _) in /_/src/Shared/E2ETesting/WaitAssert.cs:line 109

Build

https://dev.azure.com/dnceng/public/_build/results?buildId=1184103&view=ms.vss-test-web.build-test-results-tab&runId=35606222&paneView=debug&resultId=100120

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.