You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Looks like the test in question is now failing with a different error:
Error: retry.try timeout: [POST http://localhost:9515/session/7406f33d0c94c068c67a8fafc075a225/element/0.45282398259865353-6/clear] stale element reference: element is not attached to the page document
(Session info: headless chrome=70.0.3538.77)
(Driver info: chromedriver=2.42.591071 (0b695ff80972cc1a65a5cd643186d2ae582cd4ac),platform=Linux 4.15.0-1023-gcp x86_64)
at Server._post (/var/lib/jenkins/workspace/elastic+kibana+pull-request+multijob-x-pack/kibana/test/functional/services/remote/verbose_remote_logging.js:34:21)
at runRequest (/var/lib/jenkins/workspace/elastic+kibana+pull-request+multijob-x-pack/kibana/node_modules/leadfoot/Session.js:92:40)
at getFinalValue (/var/lib/jenkins/workspace/elastic+kibana+pull-request+multijob-x-pack/kibana/node_modules/dojo/_debug/Promise.ts:462:22)
at /var/lib/jenkins/workspace/elastic+kibana+pull-request+multijob-x-pack/kibana/node_modules/dojo/_debug/Promise.ts:482:11
at /var/lib/jenkins/workspace/elastic+kibana+pull-request+multijob-x-pack/kibana/node_modules/dojo/_debug/Promise.ts:393:16
at runCallbacks (/var/lib/jenkins/workspace/elastic+kibana+pull-request+multijob-x-pack/kibana/node_modules/dojo/_debug/Promise.ts:11:12)
at /var/lib/jenkins/workspace/elastic+kibana+pull-request+multijob-x-pack/kibana/node_modules/dojo/_debug/Promise.ts:317:5
at run (/var/lib/jenkins/workspace/elastic+kibana+pull-request+multijob-x-pack/kibana/node_modules/dojo/_debug/Promise.ts:237:8)
at /var/lib/jenkins/workspace/elastic+kibana+pull-request+multijob-x-pack/kibana/node_modules/dojo/_debug/nextTick.ts:44:4
at _combinedTickCallback (internal/process/next_tick.js:131:7)
at process._tickCallback (internal/process/next_tick.js:180:9)
at lastError (/var/lib/jenkins/workspace/elastic+kibana+pull-request+multijob-x-pack/kibana/test/common/services/retry/retry_for_success.js:29:9)
at retryForSuccess (/var/lib/jenkins/workspace/elastic+kibana+pull-request+multijob-x-pack/kibana/test/common/services/retry/retry_for_success.js:63:13)
at
So the results are hard to interpret - not sure why adding waits would have caused earlier failures, could be the test is flaky or there are other issues with createIndexPattern - of which I have addressed more of in PR #25414 - so with both changes maybe the test will be more stable or could need more isolated investigation. Will merge along with other PR to test further on cloud and windows to see how it performs over time.
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.
Backports the following commits to 6.x: