Skip to content
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

Net::ReadTimeout error on Windows with Capybara 2.2 #1203

Closed
mattwynne opened this issue Dec 6, 2013 · 1 comment
Closed

Net::ReadTimeout error on Windows with Capybara 2.2 #1203

mattwynne opened this issue Dec 6, 2013 · 1 comment

Comments

@mattwynne
Copy link

See https://gist.github.com/mattwynne/7821742 for the error.

This happens at the end of a Cucumber scenario on a Windows 7 box with Capybara 2.2 running Firefox. When I pinned back to Capybara 2.1 the problem went away.

@henrikedberg
Copy link

I have a related (the same?) the same problem but on Ubuntu 13.10, firefox 26.0. Stacktrace and behavior seems the same, but I don't get a timeout though.

I was not even running seleium tests when the error occurred. Maybe that was the problem? 17 scenarios are passing before one scenario fails in the After hook in cucumber.rb:8, after that all tests fail in the After hook.

Reverting to 2.1.0 or commenting out the call to reset_sessions! works.

  Component returned failure code: 0x80520015 (NS_ERROR_FILE_ACCESS_DENIED) [nsIWebNavigation.loadURI]
  Build info: version: '2.33.0', revision: '4e90c97', time: '2013-05-22 15:32:38'
  System info: os.name: 'Linux', os.arch: 'amd64', os.version: '2.6.32-358.23.2.el6.x86_64', java.version: '1.6.0_24'
  Driver info: driver.version: unknown (org.openqa.selenium.remote.ErrorHandler$UnknownServerException) (Selenium::WebDriver::Error::UnknownError)
  /home/n06497/.rvm/gems/ruby-1.9.3-p448/gems/selenium-webdriver-2.39.0/lib/selenium/webdriver/remote/response.rb:51:in `assert_ok'
  /home/n06497/.rvm/gems/ruby-1.9.3-p448/gems/selenium-webdriver-2.39.0/lib/selenium/webdriver/remote/response.rb:15:in `initialize'
  /home/n06497/.rvm/gems/ruby-1.9.3-p448/gems/selenium-webdriver-2.39.0/lib/selenium/webdriver/remote/http/common.rb:59:in `new'
  /home/n06497/.rvm/gems/ruby-1.9.3-p448/gems/selenium-webdriver-2.39.0/lib/selenium/webdriver/remote/http/common.rb:59:in `create_response'
  /home/n06497/.rvm/gems/ruby-1.9.3-p448/gems/selenium-webdriver-2.39.0/lib/selenium/webdriver/remote/http/default.rb:66:in `request'
  /home/n06497/.rvm/gems/ruby-1.9.3-p448/gems/selenium-webdriver-2.39.0/lib/selenium/webdriver/remote/http/common.rb:40:in `call'
  /home/n06497/.rvm/gems/ruby-1.9.3-p448/gems/selenium-webdriver-2.39.0/lib/selenium/webdriver/remote/bridge.rb:634:in `raw_execute'
  /home/n06497/.rvm/gems/ruby-1.9.3-p448/gems/selenium-webdriver-2.39.0/lib/selenium/webdriver/remote/bridge.rb:612:in `execute'
  /home/n06497/.rvm/gems/ruby-1.9.3-p448/gems/selenium-webdriver-2.39.0/lib/selenium/webdriver/remote/bridge.rb:110:in `get'
  /home/n06497/.rvm/gems/ruby-1.9.3-p448/gems/selenium-webdriver-2.39.0/lib/selenium/webdriver/common/navigation.rb:14:in `to'
  /home/n06497/.rvm/gems/ruby-1.9.3-p448/gems/capybara-2.2.0/lib/capybara/selenium/driver.rb:102:in `reset!'
  /home/n06497/.rvm/gems/ruby-1.9.3-p448/gems/capybara-2.2.0/lib/capybara/session.rb:79:in `reset!'
  /home/n06497/.rvm/gems/ruby-1.9.3-p448/gems/capybara-2.2.0/lib/capybara.rb:255:in `block in reset_sessions!'
  /home/n06497/.rvm/gems/ruby-1.9.3-p448/gems/capybara-2.2.0/lib/capybara.rb:255:in `each'
  /home/n06497/.rvm/gems/ruby-1.9.3-p448/gems/capybara-2.2.0/lib/capybara.rb:255:in `reset_sessions!'
  /home/n06497/.rvm/gems/ruby-1.9.3-p448/gems/capybara-2.2.0/lib/capybara/cucumber.rb:8:in `After'

ghost pushed a commit that referenced this issue Dec 20, 2013
closes #1035
closes #1214
closes #1203
closes #1198

Since it does not work with remote drivers, and somehow screws up on Windows.
jnicklas added a commit that referenced this issue Jan 6, 2014
closes #1035
closes #1214
closes #1203
closes #1198
closes #1215

Since it does not work with remote drivers, and somehow screws up on Windows.
@lock lock bot locked and limited conversation to collaborators Aug 17, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants