Closed TitouanVanBelle closed 7 years ago
Experiencing the same issue: execution expired (HTTPClient::ReceiveTimeoutError)
Xcode: Version 8.2.1 (8C1002) iOS: Version 10.2
Please update to run-loop 2.3.1 and Calabash 0.20.4
Experiencing the same issue: execution expired (HTTPClient::ConnectTimeoutError) Xcode:Version 8.2.1(8C1002) iOS:Version 10.1.1 run-loop 2.3.1 Calabash 0.20.4
calabash-ios 0.20.4> start_test_server_in_background
DEBUG: HTTP: get http://192.168.2.10:27753/1.0/health {:retries=>1, :timeout=>0.5}
DEBUG: DeviceAgent-Runner is not running
DEBUG: Sending 'TERM' to ios_device_manager process '34671'
DEBUG: Waiting for ios_device_manager with pid '34671' to terminate
DEBUG: Waited for 0.100279 seconds for ios_device_manager with pid '34671' to terminate
DEBUG: HTTP: get http://192.168.2.10:27753/1.0/health {:retries=>1, :timeout=>0.5}
DEBUG: HTTP: get http://192.168.2.10:27753/1.0/health {:retries=>1, :timeout=>0.5}
DEBUG: Waiting for DeviceAgent to launch...
SHELL: /Users/power/.rvm/gems/ruby-2.1.4/gems/run_loop-2.3.1/lib/run_loop/device_agent/bin/iOSDeviceManager install --device-id 97fa0e7c22c406c442ba682dcb70c8260a35f9e9 -a /Users/power/.rvm/gems/ruby-2.1.4/gems/run_loop-2.3.1/lib/run_loop/device_agent/ipa/DeviceAgent-Runner.app
DEBUG: Took 12.942645 seconds to install DeviceAgent
SHELL: /Users/power/.rvm/gems/ruby-2.1.4/gems/run_loop-2.3.1/lib/run_loop/device_agent/bin/iOSDeviceManager start_test --device-id 97fa0e7c22c406c442ba682dcb70c8260a35f9e9 >& /Users/power/.run-loop/xcuitest/ios-device-manager.log
DEBUG: HTTP: get http://192.168.2.10:27753/1.0/health {:retries=>1800, :timeout=>180.0}
HTTPClient::ConnectTimeoutError: execution expired
from /Users/power/.rvm/gems/ruby-2.1.4/gems/httpclient-2.8.3/lib/httpclient/session.rb:611:in `initialize'
from /Users/power/.rvm/gems/ruby-2.1.4/gems/httpclient-2.8.3/lib/httpclient/session.rb:611:in `new'
from /Users/power/.rvm/gems/ruby-2.1.4/gems/httpclient-2.8.3/lib/httpclient/session.rb:611:in `create_socket'
from /Users/power/.rvm/gems/ruby-2.1.4/gems/httpclient-2.8.3/lib/httpclient/session.rb:755:in `block in connect'
from /Users/power/.rvm/rubies/ruby-2.1.4/lib/ruby/2.1.0/timeout.rb:91:in `block in timeout'
from /Users/power/.rvm/rubies/ruby-2.1.4/lib/ruby/2.1.0/timeout.rb:101:in `call'
from /Users/power/.rvm/rubies/ruby-2.1.4/lib/ruby/2.1.0/timeout.rb:101:in `timeout'
from /Users/power/.rvm/gems/ruby-2.1.4/gems/httpclient-2.8.3/lib/httpclient/session.rb:748:in `connect'
from /Users/power/.rvm/gems/ruby-2.1.4/gems/httpclient-2.8.3/lib/httpclient/session.rb:511:in `query'
from /Users/power/.rvm/gems/ruby-2.1.4/gems/httpclient-2.8.3/lib/httpclient/session.rb:177:in `query'
from /Users/power/.rvm/gems/ruby-2.1.4/gems/httpclient-2.8.3/lib/httpclient.rb:1242:in `do_get_block'
from /Users/power/.rvm/gems/ruby-2.1.4/gems/httpclient-2.8.3/lib/httpclient.rb:1019:in `block in do_request'
from /Users/power/.rvm/gems/ruby-2.1.4/gems/httpclient-2.8.3/lib/httpclient.rb:1133:in `protect_keep_alive_disconnected'
from /Users/power/.rvm/gems/ruby-2.1.4/gems/httpclient-2.8.3/lib/httpclient.rb:1014:in `do_request'
from /Users/power/.rvm/gems/ruby-2.1.4/gems/httpclient-2.8.3/lib/httpclient.rb:856:in `request'
from /Users/power/.rvm/gems/ruby-2.1.4/gems/httpclient-2.8.3/lib/httpclient.rb:743:in `get'
... 1 levels...
from /Users/power/.rvm/gems/ruby-2.1.4/gems/run_loop-2.3.1/lib/run_loop/http/retriable_client.rb:163:in `block in request'
from /Users/power/.rvm/gems/ruby-2.1.4/gems/run_loop-2.3.1/lib/run_loop/http/retriable_client.rb:150:in `times'
from /Users/power/.rvm/gems/ruby-2.1.4/gems/run_loop-2.3.1/lib/run_loop/http/retriable_client.rb:150:in `request'
from /Users/power/.rvm/gems/ruby-2.1.4/gems/run_loop-2.3.1/lib/run_loop/http/retriable_client.rb:76:in `get'
from /Users/power/.rvm/gems/ruby-2.1.4/gems/run_loop-2.3.1/lib/run_loop/device_agent/client.rb:1244:in `health'
from /Users/power/.rvm/gems/ruby-2.1.4/gems/run_loop-2.3.1/lib/run_loop/device_agent/client.rb:1303:in `launch_cbx_runner'
from /Users/power/.rvm/gems/ruby-2.1.4/gems/run_loop-2.3.1/lib/run_loop/device_agent/client.rb:271:in `launch'
from /Users/power/.rvm/gems/ruby-2.1.4/gems/run_loop-2.3.1/lib/run_loop/device_agent/client.rb:147:in `run'
from /Users/power/.rvm/gems/ruby-2.1.4/gems/run_loop-2.3.1/lib/run_loop.rb:113:in `run'
from /Users/power/.rvm/gems/ruby-2.1.4/gems/calabash-cucumber-0.20.4/lib/calabash-cucumber/launcher.rb:408:in `block in new_run_loop'
from /Users/power/.rvm/gems/ruby-2.1.4/gems/calabash-cucumber-0.20.4/lib/calabash-cucumber/launcher.rb:406:in `times'
from /Users/power/.rvm/gems/ruby-2.1.4/gems/calabash-cucumber-0.20.4/lib/calabash-cucumber/launcher.rb:406:in `new_run_loop'
from /Users/power/.rvm/gems/ruby-2.1.4/gems/calabash-cucumber-0.20.4/lib/calabash-cucumber/launcher.rb:365:in `relaunch'
from /Users/power/.rvm/gems/ruby-2.1.4/gems/calabash-cucumber-0.20.4/lib/calabash-cucumber/core.rb:1567:in `start_test_server_in_background'
from (irb):2
Can only start the first run
Best guess: the physical device and the the host machine (your mac) are not on the same network.
Is under the same network.Network timeout is accidental I delete deviceAgent before every run cucumber, if not delete the deviceAgent cucumber always request timeout
Try updating to ruby 2.3.1.
This problem is happening on a CI machine and involves physical devices.
My policy to not answer questions about CI troubles because it is impossible for me to know what your set up is.
I delete deviceAgent before every run cucumber,
I don't recommend doing this. We believe we have resolved the issues that made this necessary for some users.
@TitouanVanBelle
Host is down - Host is down - connect(2) for "10.90.7.41" port 37265 (10.90.7.41:37265) (Errno::EHOSTDOWN) ./FyberSDK/FyberTestApp/features/support/launch.rb:62:in `After'
^ investigate what is happening in your After hook.
After upgrading my tools to run our automated tests on iOS 10, I am facing errors that seem to happen randomly. Everything works find when using the calabash-ios console.
Environment
OS: Sierra Ruby: 2.2.2 calabash-ios: 0.20.3 run_loop: 2.3.0 Device: iPhone 6s on iOS 10.2.1
Command
This is the command that I run
Results
Two Jenkins jobs ran one after the other can have different results even without any changes on the infrastructure or the scenarios in-between.
Run 1 130 scenarios (130 passed) 524 steps (524 passed) Finished in 116m25.628s seconds
Run 2 130 scenarios (15 failed, 115 passed) 524 steps (7 failed, 43 skipped, 474 passed) Finished in 151m39.875s seconds
The second run features this kind of errors
If there is anything I can add let me know.