-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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.
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
[🐛 Bug]: Intermittent session errors on previously stable test suite #14580
Comments
@duncan-bayne, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
@duncan-bayne Could you try to set |
@joerg1985 Afraid it didn't continue after I made the following change to our helper method that builds the Chromedriver options:
It's worth mentioning that some of these failures are happening at points where we do something completely innocuous like |
Does this only happen when calling a URL or are other commands affected? |
The pattern is that the error occurs on a
|
What happened?
Firstly, thanks for Selenium 🙏 We've been using it for 15 years, and have built a large and useful automated test suite with it ❤️
Recently we've been seeing intermittent session errors, in tests that have run (in some cases for years) without issues. These happen at various times in the test lifecycle, from
before(:each)
toafter(:suite)
. They take the form:Retrying the test will often cause it to pass.
We tried reproducing the failures locally. This was unsuccessful; the failures only happen in CI (running through Buildkite, inside Docker containers).
We then took the following steps to try to eliminate other causes of the intermittent failures. All were unsuccessful.
selenium-webdriver
Gem to the very latest version (4.25.0).We also tested switching from Selenium to Cuprite; when running under Cuprite, the tests worked reliably, which led us to believe the issue lies with Selenium.
How can we reproduce the issue?
We can't reproduce this outside the context of our CI system; however the debugging steps above lead me to believe it's an issue with Selenium.
If debugging on our stack could help resolve the issue, I'm very happy to look into how we might make that possible.
Relevant log output
When running Chrome in its own container via a remote browser connection, this is what we see in the logs when one of these failures occur:
When running Chromium locally on the test container, we see the following error:
Operating System
Ubuntu 22.04 LTS
Selenium version
Ruby 3.3.5
What are the browser(s) and version(s) where you see this issue?
Chrome 124, Chrome 117, Firefox 130.
What are the browser driver(s) and version(s) where you see this issue?
ChromeDriver 124.0.6367.78 (and others; see above for attempts to resolve the issue).
Are you using Selenium Grid?
No.
The text was updated successfully, but these errors were encountered: