Hello,
I’m running a java test suite against android emulator api-19. I’m testing a web application using the stock browser.
In my tests i’m performing quite a lot of screenshots by first switching driver context to NATIVE_APP, take screenshot, go back to WEBVIEW
After ~20min of smooth test execution, around ~13th test, the suite is interrupted during driver initialization.
org.openqa.selenium.SessionNotCreatedException: A new session could not be created. (Original error: An operation did not complete before its timeout expired. (
Original error: timeout: Adb command timed out after 30 seconds
(Driver info: chromedriver=2.20.353145 (343b531d31eeb933ec778dbcf7081628a13960
67),platform=Windows NT 6.2 x86_64))) (WARNING: The server did not provide any s
tacktrace information)
Command duration or timeout: 255.66 seconds
Build info: version: ‘2.48.2’, revision: ‘41bccdd10cf2c0560f637404c2d96164b67d9d
67’, time: ‘2015-10-09 13:08:06’
System info: host: ‘myhost’, ip: ‘192.168.1.123’, os.name: ‘Windows Server 2012’
, os.arch: ‘x86’, os.version: ‘6.2’, java.version: ‘1.7.0_80’
Driver info: io.appium.java_client.android.AndroidDriver
In appium log I’ve noticed that chromedriver exited unexpectedly with code null
The emulator is not responsive and I cannot logon to it with adb shell. After restarting adb manually device appear offline
Using latest android sdk, appium, chrome-driver and java client libraries. jdk 7.80
Best regards,
Bozhko