Failing test: Chrome UI Functional Tests.test/functional/apps/discover/_doc_navigation·js - discover app doc link in discover add filter should create an exists filter if value is null (#7189)

[kibanamachine]

A test failed on a tracked branch

{ StaleElementReferenceError: stale element reference: element is not attached to the page document
  (Session info: headless chrome=83.0.4103.116)
    at Object.throwDecodedError (node_modules/selenium-webdriver/lib/error.js:550:15)
    at parseHttpResponse (node_modules/selenium-webdriver/lib/http.js:565:13)
    at Executor.execute (node_modules/selenium-webdriver/lib/http.js:491:26)
    at process._tickCallback (internal/process/next_tick.js:68:7)
  name: 'StaleElementReferenceError',
  remoteStacktrace: '#0 0x5627d048f579 <unknown>\n' }

First failure: Jenkins Build

[kibanamachine]

New 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

[kibanamachine]

New failure: Jenkins Build

[kibanamachine]

New failure: Jenkins Build

[mistic]

That test has been failing a couple of times in the recent hours. I'm skipping it on master to unblock the CI.

[elasticmachine]

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

[timroes]

@lizozom This looks very similar to the issue you fixed around null filters recently? Could the failures be coming from that PR potentially?

[kertal]

@lizozom think this was fixed in #71250, wasn't it

[kertal]

according to @lizozom this can be closed, so let's close it