Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/advanced_settings/feature_controls/advanced_settings_spaces·ts - Advanced Settings spaces feature controls space with Advanced Settings disabled redirects to management home

[kibanamachine]

A test failed on a tracked branch

Error: expected testSubject(managementHome) to exist
    at TestSubjects.existOrFail (/dev/shm/workspace/kibana/test/functional/services/test_subjects.ts:60:15)

First 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-app (Team:KibanaApp)

[kibanamachine]

New failure: Jenkins Build

[kibanamachine]

New failure: Jenkins Build

[spalger]

This has failed 7 builds in the last week

Skipped

master: a7bebba
7.x/7.8: 12f6b73

[dej611]

Cannot reproduce on the flaky test runner: https://kibana-ci.elastic.co/job/kibana+flaky-test-suite-runner/644/

[spalger]

The skip was a while ago, and the failure that finally triggered the skip was in 7.8. It's possible that this was fixed in a newer version but try cherry-picking dej611@c126365 to 7.8 and running that in the flaky test runner. The fix might not have made it back to 7.8. Alternatively, a PR with nothing but removing the skip that has 300-400 successful flaky test executions would be more than enough "evidence" that the test is no longer flaky.

[dej611]

Flaky test runner batches:

• 100 execution - ✅ 0/100 failures
• 100 execution - ✅ 0/100 failures
• 100 execution - ✅ 0/100 failures

🎉

Note: I had to filter out other (non-functional) X-Pack Group: 2 suites to make it run for 100 executions, in order to reduce the amount of work.
The skip has been removed and all the functional tests have run for 300 times.