AuthTest.AuthorizeViewCases_RequirePolicy_Authorized()

[dougbu]

Error Message

OpenQA.Selenium.WebDriverException : unknown error: net::ERR_ADDRESS_IN_USE\n  (Session info: headless chrome=91.0.4472.101)

then with a newer Chrome

OpenQA.Selenium.WebDriverException : unknown error: net::ERR_ADDRESS_IN_USE\n  (Session info: headless chrome=91.0.4472.106)

Stacktrace

   at OpenQA.Selenium.Remote.RemoteWebDriver.UnpackAndThrowOnError(Response errorResponse) in WebDriver.dll:token 0x600053b+0x12e
   at OpenQA.Selenium.Remote.RemoteWebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters) in WebDriver.dll:token 0x6000535+0x4a
   at OpenQA.Selenium.Remote.RemoteWebDriver.set_Url(String value) in WebDriver.dll:token 0x60004fb+0x2d
   at OpenQA.Selenium.Remote.RemoteNavigator.GoToUrl(Uri url) in WebDriver.dll:token 0x60004c4+0x29
   at Microsoft.AspNetCore.Components.E2ETest.BasicTestAppAuthenticationWebDriverExtensions.SignInAs(IWebDriver browser, Uri baseUri, String usernameOrNull, String rolesOrNull, Boolean useSeparateTab) in /_/src/Components/test/E2ETest/Infrastructure/WebDriverExtensions/BasicTestAppAuthenticationWebDriverExtensions.cs:line 33
   at Microsoft.AspNetCore.Components.E2ETest.Tests.AuthTest.SignInAs(String userName, String roles, Boolean useSeparateTab) in /_/src/Components/test/E2ETest/Tests/AuthTest.cs:line 239
   at Microsoft.AspNetCore.Components.E2ETest.Tests.AuthTest.AuthorizeViewCases_RequirePolicy_Authorized() in /_/src/Components/test/E2ETest/Tests/AuthTest.cs:line 127

Build

Test failed in aspnetcore-ci builds of our main branch:

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

Both failures were in our Windows non-Helix test jobs.

[javiercn]

@dougbu thanks for bringing this up.

This seems like some Selenium related instability.

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.

[pranavkm]

@BrennanConroy our suspicion is that this might be related to the most recent Selenium update. Could you try reverting the most recent update to see if it fixes the issue? Thanks!

dfe8bd2#diff-1ea18ff65faa2ae6fed570b83747086d0317f5e4bc325064f6c14319a9c4ff67

[BrennanConroy]

You realize there is no difference between those two versions right?
jsakamoto/nupkg-selenium-webdriver-chromedriver@v.91.0.4472.1900-beta...v.91.0.4472.1900