Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/reporting_management/report_listing·ts - reporting management app Listing of Reports Paginates content

[kibanamachine]

A test failed on a tracked branch

{ StaleElementReferenceError: stale element reference: element is not attached to the page document
  (Session info: headless chrome=84.0.4147.125)
    at Object.throwDecodedError (/dev/shm/workspace/kibana/node_modules/selenium-webdriver/lib/error.js:550:15)
    at parseHttpResponse (/dev/shm/workspace/kibana/node_modules/selenium-webdriver/lib/http.js:565:13)
    at Executor.execute (/dev/shm/workspace/kibana/node_modules/selenium-webdriver/lib/http.js:491:26)
    at process._tickCallback (internal/process/next_tick.js:68:7)
  name: 'StaleElementReferenceError',
  remoteStacktrace: '#0 0x55ca90dc5ea9 <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

[elasticmachine]

Pinging @elastic/kibana-reporting-services (Team:Reporting Services)

[azasypkin]

[jbudz]

skipped ^. adding blocker label, atleast until triage

[tsullivan]

Thanks @jbudz, this test was just merged recently. It looks like it coincidentally wasn't flaky in the PR