Fix Windows IE test timeouts in Events and Fetch service #8969
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Kibana version: master (6.0.0-alpha1)
Elasticsearch version: master
Server OS version: Windows 10
Browser version: IE 11
Browser OS version: Windows 10
Original install method (e.g. download page, yum, from source, etc.): dev testing
Description of the problem including expected versus actual behavior: Several browser tests are failing for me on Windows 10 with IE 11. At least one of them is a timeout at 10s. If I bump the timeout up to 20 seconds they pass. We know IE is slower than other browsers at some tasks. I think we should bump the timeout up to avoid false failures.
OR - is this really unacceptable performance on these tasks and we need to look into it instead of making the timeout longer?
Steps to reproduce:
npm run test:dev
http://localhost:9876/debug.html?grep=Fetch%20service
http://localhost:9876/debug.html?grep=Fetch%20service
Fetch service
#doc(docSource)
✓
fetches a single doc source7883ms
‣
#search(searchSource)
✖
fetches a single search source
‣
Error: timeout of 10000ms exceeded. Ensure the done() callback is being called in this test.
This test above passed when I changed the timeout to 20000ms. It actually passed in 9541ms in this case.
Passed again in 9698ms
Passed again in 10606ms
With some load applied on my laptop I can get them well past 10s;
Same with Events tests;