Index pattern feature control test failures

[liza-mae]

**✖ fail: "Index Patterns feature controls security global index_patterns all privileges "before all" hook" **
│ Error: Timeout of 360000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.
✖ fail: "Index Patterns feature controls security global index_patterns all privileges "after all" hook"
│ Error: retry.try timeout: ElementClickInterceptedError: element click intercepted: Element ... is not clickable at point (1576, 24). Other element would receive the click:

...
│ (Session info: headless chrome=74.0.3729.108)
│ (Driver info: chromedriver=74.0.3729.6 (255758eccf3d244491b8a1317aa76e1ce10d57e9-refs/branch-heads/3729@{#29}),platform=Linux 4.4.0-142-generic x86_64)
│ at Object.checkLegacyResponse (/home/liza/TESTING/kbn-cloud-testing/node_modules/selenium-webdriver/lib/error.js:585:15)
│ at parseHttpResponse (/home/liza/TESTING/kbn-cloud-testing/node_modules/selenium-webdriver/lib/http.js:533:13)
│ at Executor.execute (/home/liza/TESTING/kbn-cloud-testing/node_modules/selenium-webdriver/lib/http.js:468:26)
│ at process._tickCallback (internal/process/next_tick.js:68:7)
│ at lastError (/home/liza/TESTING/kbn-cloud-testing/test/common/services/retry/retry_for_success.ts:28:9)
│ at onFailure (/home/liza/TESTING/kbn-cloud-testing/test/common/services/retry/retry_for_success.ts:68:13)

** ✖ fail: "Index Patterns feature controls security global index_patterns read-only privileges "before all" hook" **
│ Error: Timeout of 360000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

Version: 7.2

[elasticmachine]

Pinging @elastic/kibana-test-triage

[elasticmachine]

Pinging @elastic/kibana-app

[liza-mae]

Failures are related to #39689

[flash1293]

@liza-mae after checking locally I can confirm this test failure is caused by the welcome screen problem. Does it make sense to keep these open (e.g. also #39367) when all of the failures are caused by a single root cause tracked in #39689?

[liza-mae]

@flash1293 thanks, I fixed this on staging as part of #39689. So we can close this.

[liza-mae]

@flash1293 answer to your question - initially I manually went through the failures and tried to reduce the number by tracking down the root cause and creating one issue, however this became time consuming for me as there were too many failures :) So now I automatically create the issues and since I don't bail on failure to run all the tests, cascading failures will unfortunately also be opened. I am hoping once we have the team knock down these test failures this number should be low or zero in the future :)