-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Scripts fail with reason Failed: timeout #5152
Description
Hi there!
I have around 150 Test scenarios in different feature files, that run every day. All the scenarios run perfectly some days but sometimes, we are seeing Failed: timeout with out any specific reason.
Below is the Protractor config file.
exports.config = {
//seleniumAddress: 'http://localhost:4444/wd/hub',
specs: ['./features/login_test.js', './features/login_errors_test.js', './features/settings_test.js'],
framework: 'jasmine2',
capabilities: {
browserName: 'chrome',
},
jasmineNodeOpts: {
defaultTimeoutInterval: 6000000
},
}
Below is the error seen after few scenarios passed, from here all the scripts do fail.
Failed: timeout (Session info: headless chrome=71.0.3578.98) (Driver info: chromedriver=2.46.628411 (3324f4c8be9ff2f70a05a30ebc72ffb013e1a71e),platform=Mac OS X 10.13.6 x86_64)
stdout:
TimeoutError: timeout
(Session info: headless chrome=71.0.3578.98)
(Driver info: chromedriver=2.46.628411 (3324f4c8be9ff2f70a05a30ebc72ffb013e1a71e),platform=Mac OS X 10.13.6 x86_64)
at Object.checkLegacyResponse (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/error.js:546:15)
at parseHttpResponse (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/http.js:509:13)
at doSend.then.response (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/http.js:441:30)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
From: Task: WebDriver.navigate().to(https://myurl.com)
Any help would be appreciated to handle the above!
Bug report
- Node Version:
8.12.0 - Browser(s):
Chrome - Operating System and Version
Windows 8.1 and Mac OS X 10