Skip to content

Test failures and hangs due to Selenium/Chrome issues #25322

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
JunTaoLuo opened this issue Aug 27, 2020 · 1 comment · Fixed by #25330
Closed

Test failures and hangs due to Selenium/Chrome issues #25322

JunTaoLuo opened this issue Aug 27, 2020 · 1 comment · Fixed by #25330
Labels
area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework

Comments

@JunTaoLuo
Copy link
Contributor

We have seen a lot of CI failures/hangs in due to issues with Chrome and Selenium. The investigation is ongoing but the affected tests have been disabled to unblock CI. This issue tracks fixing those tests and re-enabling them.
@JunTaoLuo JunTaoLuo added the area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework label Aug 27, 2020
This was referenced Aug 27, 2020
Merged
Merged
@BrennanConroy BrennanConroy mentioned this issue Sep 8, 2020
Merged
@SteveSandersonMS
Copy link
Member

Note that the fix here also needs to be backported to release/3.1 so the tests can be enabled there too.

@ghost ghost locked as resolved and limited conversation to collaborators Oct 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix chrome/selenium tests dotnet/aspnetcore
3 participants
@SteveSandersonMS @JunTaoLuo and others