Hi,

Based on my exp, It may occurs in 3 diff condition

1. Internet limit crossed
2. Connection interrupt between test server and browser.
3. Memory allocation issue


Solution : Get a help from System Admin to debug this issue. Nothing is
required in code level(If u r very good in Ruby memory allocation code then
u can handle it in better way )

Thanks


On Sat, Nov 23, 2013 at 4:11 PM, Ragavan Ambighananthan <
eelam.raga...@gmail.com> wrote:

> looks like your browser crashed or closed by 'some other way' before you
> close it in your teardown because this exception happens when you are doing
> @browser.close
>
> gems/watir-webdriver-0.6.2/lib/watir-webdriver/browser.rb:135:in `close'
>
>
> i have seen this during parallel execution in the same box or sometimes 
> browser get closed due to some other reasons.
>
>
> On Tuesday, November 12, 2013 10:08:04 PM UTC, Royce King wrote:
>>
>> I have an issue with my watir tests.  I am in the process of migrating to
>> a new firewall, and when behind my old firewall the tests work as designed.
>>  But when I move my test server behind my new firewall I get the following
>> error.
>>
>> /var/lib/jenkins/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/net/protocol.rb:146:in
>>  `rescue in rbuf_fill': Timeout::Error (Timeout::Error)
>>      from 
>> /var/lib/jenkins/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/net/protocol.rb:140:in
>>  `rbuf_fill'
>>      from 
>> /var/lib/jenkins/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/net/protocol.rb:122:in
>>  `readuntil'
>>      from 
>> /var/lib/jenkins/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/net/protocol.rb:132:in
>>  `readline'
>>      from 
>> /var/lib/jenkins/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/net/http.rb:2562:in
>>  `read_status_line'
>>      from 
>> /var/lib/jenkins/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/net/http.rb:2551:in
>>  `read_new'
>>      from 
>> /var/lib/jenkins/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/net/http.rb:1319:in
>>  `block in transport_request'
>>      from 
>> /var/lib/jenkins/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/net/http.rb:1316:in
>>  `catch'
>>      from 
>> /var/lib/jenkins/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/net/http.rb:1316:in
>>  `transport_request'
>>      from 
>> /var/lib/jenkins/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/net/http.rb:1293:in
>>  `request'
>>      from 
>> /var/lib/jenkins/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/net/http.rb:1286:in
>>  `block in request'
>>      from 
>> /var/lib/jenkins/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/net/http.rb:745:in
>>  `start'
>>      from 
>> /var/lib/jenkins/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/net/http.rb:1284:in
>>  `request'
>>      from 
>> /var/lib/jenkins/workspace/watir-test/vendor/bundle/ruby/1.9.1/gems/selenium-webdriver-2.29.0/lib/selenium/webdriver/remote/http/default.rb:83:in
>>  `response_for'
>>      from 
>> /var/lib/jenkins/workspace/watir-test/vendor/bundle/ruby/1.9.1/gems/selenium-webdriver-2.29.0/lib/selenium/webdriver/remote/http/default.rb:39:in
>>  `request'
>>      from 
>> /var/lib/jenkins/workspace/watir-test/vendor/bundle/ruby/1.9.1/gems/selenium-webdriver-2.29.0/lib/selenium/webdriver/remote/http/common.rb:40:in
>>  `call'
>>      from 
>> /var/lib/jenkins/workspace/watir-test/vendor/bundle/ruby/1.9.1/gems/selenium-webdriver-2.29.0/lib/selenium/webdriver/remote/bridge.rb:615:in
>>  `raw_execute'
>>      from 
>> /var/lib/jenkins/workspace/watir-test/vendor/bundle/ruby/1.9.1/gems/selenium-webdriver-2.29.0/lib/selenium/webdriver/remote/bridge.rb:593:in
>>  `execute'
>>      from 
>> /var/lib/jenkins/workspace/watir-test/vendor/bundle/ruby/1.9.1/gems/selenium-webdriver-2.29.0/lib/selenium/webdriver/remote/bridge.rb:189:in
>>  `quit'
>>      from 
>> /var/lib/jenkins/workspace/watir-test/vendor/bundle/ruby/1.9.1/gems/selenium-webdriver-2.29.0/lib/selenium/webdriver/chrome/bridge.rb:48:in
>>  `quit'
>>      from 
>> /var/lib/jenkins/workspace/watir-test/vendor/bundle/ruby/1.9.1/gems/selenium-webdriver-2.29.0/lib/selenium/webdriver/common/driver.rb:168:in
>>  `quit'
>>      from 
>> /var/lib/jenkins/workspace/watir-test/vendor/bundle/ruby/1.9.1/gems/watir-webdriver-0.6.2/lib/watir-webdriver/browser.rb:135:in
>>  `close'
>>      from taxes2012login.rb:149:in `after_suite'
>>      from /var/lib/jenkins/workspace/watir-test/minitest_runner.rb:26:in 
>> `_run_suite'
>>      from 
>> /var/lib/jenkins/workspace/watir-test/vendor/bundle/ruby/1.9.1/gems/minitest-4.6.1/lib/minitest/unit.rb:886:in
>>  `block in _run_suites'
>>      from 
>> /var/lib/jenkins/workspace/watir-test/vendor/bundle/ruby/1.9.1/gems/minitest-4.6.1/lib/minitest/unit.rb:886:in
>>  `map'
>>      from 
>> /var/lib/jenkins/workspace/watir-test/vendor/bundle/ruby/1.9.1/gems/minitest-4.6.1/lib/minitest/unit.rb:886:in
>>  `_run_suites'
>>      from /var/lib/jenkins/workspace/watir-test/minitest_runner.rb:15:in 
>> `_run_suites'
>>      from 
>> /var/lib/jenkins/workspace/watir-test/vendor/bundle/ruby/1.9.1/gems/minitest-4.6.1/lib/minitest/unit.rb:856:in
>>  `_run_anything'
>>      from 
>> /var/lib/jenkins/workspace/watir-test/vendor/bundle/ruby/1.9.1/gems/minitest-4.6.1/lib/minitest/unit.rb:1063:in
>>  `run_tests'
>>      from 
>> /var/lib/jenkins/workspace/watir-test/vendor/bundle/ruby/1.9.1/gems/minitest-4.6.1/lib/minitest/unit.rb:1050:in
>>  `block in _run'
>>      from 
>> /var/lib/jenkins/workspace/watir-test/vendor/bundle/ruby/1.9.1/gems/minitest-4.6.1/lib/minitest/unit.rb:1049:in
>>  `each'
>>      from 
>> /var/lib/jenkins/workspace/watir-test/vendor/bundle/ruby/1.9.1/gems/minitest-4.6.1/lib/minitest/unit.rb:1049:in
>>  `_run'
>>      from 
>> /var/lib/jenkins/workspace/watir-test/vendor/bundle/ruby/1.9.1/gems/minitest-4.6.1/lib/minitest/unit.rb:1037:in
>>  `run'
>>      from 
>> /var/lib/jenkins/workspace/watir-test/vendor/bundle/ruby/1.9.1/gems/minitest-4.6.1/lib/minitest/unit.rb:778:in
>>  `block in autorun'
>>
>>
>>
>> I don't know why I would be getting a timeout error.  The test server is
>> in the same vlan as my web servers so there is no firewall rule that is
>> restricting it.  All I am doing is changing the gateway to the new
>> Firewall.  Any ideas on what could causing the timeout error?
>>
>> Here are the versions of my gems.
>>
>> headless (1.0.0)
>>
>> selenium-webdriver (2.29.0)
>> watir-webdriver (0.6.2)
>>
>>
>> Thanks for the help.
>> Royce
>>
>>
>>  --
> --
> Before posting, please read http://watir.com/support. In short: search
> before you ask, be nice.
>
> watir-general@googlegroups.com
> http://groups.google.com/group/watir-general
> watir-general+unsubscr...@googlegroups.com
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Watir General" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to watir-general+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>



-- 
Regards,
P.Raveendran
http://raveendran.wordpress.com

-- 
-- 
Before posting, please read http://watir.com/support. In short: search before 
you ask, be nice.

watir-general@googlegroups.com
http://groups.google.com/group/watir-general
watir-general+unsubscr...@googlegroups.com

--- 
You received this message because you are subscribed to the Google Groups 
"Watir General" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to watir-general+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to