2013-05-31 22 views
14

sto correndo:Watir Chrome Driver "EOFError: fine del file ha raggiunto" Errore

Chrome versione google-chrome-stable/sconosciuto uptodate 27.0.1453.93-r200836

Debian GNU/Linux 6.0.6 (squeeze) 32x

Quando provo a fare funzionare:

require 'watir-webdriver' 
require 'headless' 
headless = Headless.new 
headless.start 
b = Watir::Browser.new(:chrome) 

ottengo:

EOFError: end of file reached 
     from /usr/local/rvm/rubies/ruby-1.9.3-p429/lib/ruby/1.9.1/net/protocol.rb:141:in `read_nonblock' 
     from /usr/local/rvm/rubies/ruby-1.9.3-p429/lib/ruby/1.9.1/net/protocol.rb:141:in `rbuf_fill' 
     from /usr/local/rvm/rubies/ruby-1.9.3-p429/lib/ruby/1.9.1/net/protocol.rb:122:in `readuntil' 
     from /usr/local/rvm/rubies/ruby-1.9.3-p429/lib/ruby/1.9.1/net/protocol.rb:132:in `readline' 
     from /usr/local/rvm/rubies/ruby-1.9.3-p429/lib/ruby/1.9.1/net/http.rb:2563:in `read_status_line' 
     from /usr/local/rvm/rubies/ruby-1.9.3-p429/lib/ruby/1.9.1/net/http.rb:2552:in `read_new' 
     from /usr/local/rvm/rubies/ruby-1.9.3-p429/lib/ruby/1.9.1/net/http.rb:1320:in `block in transport_request' 
     from /usr/local/rvm/rubies/ruby-1.9.3-p429/lib/ruby/1.9.1/net/http.rb:1317:in `catch' 
     from /usr/local/rvm/rubies/ruby-1.9.3-p429/lib/ruby/1.9.1/net/http.rb:1317:in `transport_request' 
     from /usr/local/rvm/rubies/ruby-1.9.3-p429/lib/ruby/1.9.1/net/http.rb:1294:in `request' 
     from /usr/local/rvm/rubies/ruby-1.9.3-p429/lib/ruby/1.9.1/net/http.rb:1287:in `block in request' 
     from /usr/local/rvm/rubies/ruby-1.9.3-p429/lib/ruby/1.9.1/net/http.rb:746:in `start' 
     from /usr/local/rvm/rubies/ruby-1.9.3-p429/lib/ruby/1.9.1/net/http.rb:1285:in `request' 
     from /usr/local/rvm/gems/ruby-1.9.3-p429/gems/selenium-webdriver-2.33.0/lib/selenium/webdriver/remote/http/default.rb:83:in `response_for' 
     from /usr/local/rvm/gems/ruby-1.9.3-p429/gems/selenium-webdriver-2.33.0/lib/selenium/webdriver/remote/http/default.rb:39:in `request' 
     from /usr/local/rvm/gems/ruby-1.9.3-p429/gems/selenium-webdriver-2.33.0/lib/selenium/webdriver/remote/http/common.rb:40:in `call' 
     from /usr/local/rvm/gems/ruby-1.9.3-p429/gems/selenium-webdriver-2.33.0/lib/selenium/webdriver/remote/bridge.rb:629:in `raw_execute' 
     from /usr/local/rvm/gems/ruby-1.9.3-p429/gems/selenium-webdriver-2.33.0/lib/selenium/webdriver/remote/bridge.rb:98:in `create_session' 
     from /usr/local/rvm/gems/ruby-1.9.3-p429/gems/selenium-webdriver-2.33.0/lib/selenium/webdriver/remote/bridge.rb:68:in `initialize' 
     from /usr/local/rvm/gems/ruby-1.9.3-p429/gems/selenium-webdriver-2.33.0/lib/selenium/webdriver/chrome/bridge.rb:29:in `initialize' 
     from /usr/local/rvm/gems/ruby-1.9.3-p429/gems/selenium-webdriver-2.33.0/lib/selenium/webdriver/common/driver.rb:37:in `new' 
     from /usr/local/rvm/gems/ruby-1.9.3-p429/gems/selenium-webdriver-2.33.0/lib/selenium/webdriver/common/driver.rb:37:in `for' 
     from /usr/local/rvm/gems/ruby-1.9.3-p429/gems/selenium-webdriver-2.33.0/lib/selenium/webdriver.rb:67:in `for' 
     from /usr/local/rvm/gems/ruby-1.9.3-p429/gems/watir-webdriver-0.6.4/lib/watir-webdriver/browser.rb:46:in `initialize' 
     from (irb):7:in `new' 
     from (irb):7 
     from /usr/local/rvm/rubies/ruby-1.9.3-p429/bin/irb:16:in `<main>' 

Non sono davvero sicuro di come iniziare a risolvere questo problema. Sto cercando google ma non trovo nessuna correzione che funzioni per me finora. Speriamo che qualcuno possa aiutare con questo.

+1

Si può iniziare condividendo il sistema operativo e la versione. –

+0

Versione Chrome google-chrome-stable/uptodate sconosciuto 27.0.1453.93-r200836, Debian GNU/Linux 6.0.6 (squeeze) 32x – newUserNameHere

+1

newUserNameHere: Hai il chromedriver nel tuo PATH? –

risposta

2

Quindi sono tornato a questo alcuni mesi più tardi. Sembra che tutto ciò che questo ha causato in origine questo è stato risolto quando ho scaricato l'ultima chromedriver disponibile qui:

http://chromedriver.storage.googleapis.com/index.html

Attualmente che la versione è 2.9

+0

Se sul sistema sono presenti più file chromedriver, "which chromedriver" e "chromedriver --version" potrebbero puntare a un chromedriver diverso da quello che vede il Selenium. Esegui un comando find per individuare tutti i file denominati "chromedriver" e rimuoverli prima di posizionare la versione più recente dal link sopra nel tuo/usr/local/bin e dovrebbe funzionare – emery