dashboard app using current data test failures

[liza-mae]

Chrome UI Functional Tests.test/functional/apps/dashboard/panel_expand_toggle·js.dashboard app using current data expanding a panel "before all" hook 

Stack Trace

Error: retry.try timeout: ElementClickInterceptedError: element click intercepted: Element Dashboard is not clickable at point (101, 23). Other element would receive the click:

(Session info: headless chrome=75.0.3770.142) (Driver info: chromedriver=75.0.3770.90 (a6dcaf7e3ec6f70a194cc25e8149475c6590e025-refs/branch-heads/3770@{#1003}),platform=Linux 4.16.13-200.fc27.x86_64 x86_64) at Object.checkLegacyResponse (node_modules/selenium-webdriver/lib/error.js:585:15) at parseHttpResponse (node_modules/selenium-webdriver/lib/http.js:551:13) at Executor.execute (node_modules/selenium-webdriver/lib/http.js:486:26) at process._tickCallback (internal/process/next_tick.js:68:7) at lastError (test/common/services/retry/retry_for_success.ts:28:9) at onFailure (test/common/services/retry/retry_for_success.ts:68:13)  

Chrome UI Functional Tests.test/functional/apps/dashboard/dashboard_grid·js.dashboard app using current data dashboard grid "before all" hook 

Stack Trace

Error: retry.try timeout: ElementClickInterceptedError: element click intercepted: Element Dashboard is not clickable at point (101, 23). Other element would receive the click:

(Session info: headless chrome=75.0.3770.142) (Driver info: chromedriver=75.0.3770.90 (a6dcaf7e3ec6f70a194cc25e8149475c6590e025-refs/branch-heads/3770@{#1003}),platform=Linux 4.16.13-200.fc27.x86_64 x86_64) at Object.checkLegacyResponse (node_modules/selenium-webdriver/lib/error.js:585:15) at parseHttpResponse (node_modules/selenium-webdriver/lib/http.js:551:13) at Executor.execute (node_modules/selenium-webdriver/lib/http.js:486:26) at process._tickCallback (internal/process/next_tick.js:68:7) at lastError (test/common/services/retry/retry_for_success.ts:28:9) at onFailure (test/common/services/retry/retry_for_success.ts:68:13)  

Chrome UI Functional Tests.test/functional/apps/dashboard/view_edit·js.dashboard app using current data dashboard view edit mode "before all" hook 

Stack Trace

Error: retry.try timeout: ElementClickInterceptedError: element click intercepted: Element Dashboard is not clickable at point (101, 23). Other element would receive the click:

(Session info: headless chrome=75.0.3770.142) (Driver info: chromedriver=75.0.3770.90 (a6dcaf7e3ec6f70a194cc25e8149475c6590e025-refs/branch-heads/3770@{#1003}),platform=Linux 4.16.13-200.fc27.x86_64 x86_64) at Object.checkLegacyResponse (node_modules/selenium-webdriver/lib/error.js:585:15) at parseHttpResponse (node_modules/selenium-webdriver/lib/http.js:551:13) at Executor.execute (node_modules/selenium-webdriver/lib/http.js:486:26) at process._tickCallback (internal/process/next_tick.js:68:7) at lastError (test/common/services/retry/retry_for_success.ts:28:9) at onFailure (test/common/services/retry/retry_for_success.ts:68:13)  

Chrome UI Functional Tests.test/functional/apps/dashboard/index·js.dashboard app using current data "after all" hook: unloadCurrentData 

Stack Trace

{ ElementClickInterceptedError: element click intercepted: Element ... is not clickable at point (24, 162). Other element would receive the click:

(Session info: headless chrome=75.0.3770.142) (Driver info: chromedriver=75.0.3770.90 (a6dcaf7e3ec6f70a194cc25e8149475c6590e025-refs/branch-heads/3770@{#1003}),platform=Linux 4.16.13-200.fc27.x86_64 x86_64) at Object.checkLegacyResponse (node_modules/selenium-webdriver/lib/error.js:585:15) at parseHttpResponse (node_modules/selenium-webdriver/lib/http.js:551:13) at Executor.execute (node_modules/selenium-webdriver/lib/http.js:486:26) at process._tickCallback (internal/process/next_tick.js:68:7) name: 'ElementClickInterceptedError', remoteStacktrace: '' }

Version: master

[elasticmachine]

Pinging @elastic/kibana-app

[elasticmachine]

Pinging @elastic/kibana-test-triage

[majagrubic]

I don't know if there have been any failures of these tests since July. They seem pretty stable lately.
I am not sure if there's much we can do 5 months later, without the full stack trace & snapshots generated by the tests. I am in favor of closing this and investigating if it re-occurs.

[liza-mae]

Agreed @majagrubic let's close this.