Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/graph/graph·ts - graph app graph should show venn when clicking a line

[kibanamachine]

A test failed on a tracked branch

{ ElementClickInterceptedError: element click intercepted: Element <line class="gphEdge" stroke-linecap="round" style="stroke-width: 5.19165;" x1="308.9892989365611" y1="329.59425273517564" x2="394.9695588066817" y2="263.9725429862544"></line> is not clickable at point (398, 459). Other element would receive the click: <svg xmlns="http://www.w3.org/2000/svg" class="gphGraph" width="100%" height="100%" pointer-events="all" id="graphSvg">...</svg>
  (Session info: headless chrome=79.0.3945.88)
  (Driver info: chromedriver=79.0.3945.36 (3582db32b33893869b8c1339e8f4d9ed1816f143-refs/branch-heads/3945@{#614}),platform=Linux 4.14.35-1902.8.4.el7uek.x86_64 x86_64)
    at Object.checkLegacyResponse (/dev/shm/workspace/kibana/node_modules/selenium-webdriver/lib/error.js:585:15)
    at parseHttpResponse (/dev/shm/workspace/kibana/node_modules/selenium-webdriver/lib/http.js:554:13)
    at Executor.execute (/dev/shm/workspace/kibana/node_modules/selenium-webdriver/lib/http.js:489:26)
    at process._tickCallback (internal/process/next_tick.js:68:7) name: 'ElementClickInterceptedError', remoteStacktrace: '' }

First failure: Jenkins Build

[elasticmachine]

Pinging @elastic/kibana-test-triage (failed-test)

[kibanamachine]

New failure: Jenkins Build

[kibanamachine]

New failure: Jenkins Build

[kibanamachine]

New failure: Jenkins Build

[spalger]

This has caused failures in 4 PRs in the last 24 hours, going all the way back to 7.6...

Skipped

master: fdd0c47
7.x/7.9: 9a9aef6
7.8: 40199f2

[elasticmachine]

Pinging @elastic/kibana-app (Team:KibanaApp)

[kibanamachine]

New failure: Jenkins Build

[flash1293]

New theory: This happens when the two vertices end up relatively below each other - I could try to stabilize this by giving the force layout a little push and trying again, but at that point I think I will simply click the line programmatically using a browser side script. It's better than nothing but this interaction is just too unpredictable.

[kibanamachine]

New failure: Jenkins Build

[kibanamachine]

New failure: kibana-on-merge - main

[stratoula]

Wooow opened after 4 years 😂 Joe you can always contribute 😄

[flash1293]

WebDriverError: unknown error: session deleted because of page crash
from unknown error: cannot determine loading status
from tab crashed
  (Session info: chrome=124.0.6367.118)
    at Object.throwDecodedError (node_modules/selenium-webdriver/lib/error.js:521:15)

Looks like an infrastructure issue, closing for now (fingers crossed)