-
Notifications
You must be signed in to change notification settings - Fork 2.3k
IE Drivers often time out when loading a page #1052
Comments
They fail due to IE flakiness most of the time, see angular#1052.
They fail due to IE flakiness most of the time, see angular#1052.
They fail due to IE flakiness most of the time, see angular#1052.
They fail due to IE flakiness most of the time, see angular#1052.
They fail due to IE flakiness most of the time, see angular#1052.
They fail due to IE flakiness most of the time, see angular#1052.
They fail due to IE flakiness most of the time, see angular#1052.
They fail due to IE flakiness most of the time, see angular#1052.
They fail due to IE flakiness most of the time, see angular#1052.
They fail due to IE flakiness most of the time, see #1052.
Any update on this? Is what I am doing related? It still times out after 10ms even after changing the threshold. This is what I get:
exports.config = {
'seleniumAddress' : 'http://hub.browserstack.com/wd/hub',
'allScriptsTimeout' : 60000,
'getPageTimeout' : 60000,
'baseUrl' : 'http://localhost:8080',
'framework' : 'jasmine',
'rootElement' : 'body',
'multiCapabilities' : capabilities,
'maxSessions' : 5,
'specs' : [ 'e2e/**/*.js' ],
'jasmineNodeOpts' : {
'defaultTimeoutInterval' : 60000,
'showColors' : true,
'includeStackTrace' : true,
'isVerbose' : true
}
}; |
I have 100% reproducibility on the message:
in IE11 in my app that otherwise tests fine with Chrome/Firefox (checked on IE11 on Windows 8.1 on BrowserStack). |
Hi, good morning, i have a problem with ie11, my test is unable to find an element into a header block, works correctly in chrome and firefox. I'm using protractor and jasmine framework. [ie #3] The last active task was: and exit reason: [ie #3] timeout: timed out after 30000 msec waiting for spec to complete cheers |
See also #1999 |
We've had issues reproducing this regularly in #1999. I'm going to close this issue. For anyone that continues to experience issues in IE: please open a new issue with a small reproducible example that we can work on together. That will hopefully keep the discussion focused. |
The errors we see most often with IE driver are
The text was updated successfully, but these errors were encountered: