Failing test: Chrome UI Functional Tests.test/functional/apps/discover/_inspector·js - discover app inspect should display request stats with no results

[kibanamachine]

A test failed on a tracked branch

        TypeError: Cannot read property '1' of undefined
    at getHitCount (test/functional/apps/discover/_inspector.js:34:29)
    at Context.getHitCount (test/functional/apps/discover/_inspector.js:57:14)
    at process._tickCallback (internal/process/next_tick.js:68:7)
      

First failure: Jenkins Build

[elasticmachine]

Pinging @elastic/kibana-test-triage

[spalger]

aborted

[kibanamachine]

New failure: Jenkins Build

[spalger]

Unlike the initial error this seems to be a legit failure which has picked up recently with 11 failures, mostly in PRs, but now spreading to master and likely 7.x soon.

New error:

Error: retry.try timeout: NoSuchElementError: no such element: Unable to locate element: {"method":"css selector","selector":"tbody"}
  (Session info: headless chrome=84.0.4147.135)
    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)
    at onFailure (test/common/services/retry/retry_for_success.ts:28:9)
    at retryForSuccess (test/common/services/retry/retry_for_success.ts:68:13)

Skipped

master: abb1cbf
7.x/7.10: a3e20d7

[elasticmachine]

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

[kertal]

this was the screen when it failed the last time:

[dej611]

It seems last time it was breaking it was September 25th:

It tested with the flaky runner this suite in isolation and could not get it to break:

• 25 runs with suite in isolation
• 100 runs with suite in isolation
• 200 runs with suite in isolation

Maybe I will give a try with the parent suite on the flaky runner.

[kertal]

I think there might be an underlying problem here, cause here's another similar error:

#78689

So not to run it in isolation is a good idea

[dej611]

Had a try also with the parent suite on the flaky runner:

• 25 runs with parent suite ✅
• 100 runs with parent suite ❌ 1 failure associated with Failing test: Chrome UI Functional Tests.test/functional/apps/discover/_field_data·js - discover app discover tab field data search php should show the correct hit count #78689

I'd probably try to fix #78689 before this issue as I could not easily isolate the bug, and it may be associated with some dirty state of that previous one.