Failing test: Firefox XPack UI Functional Tests.x-pack/test/functional/apps/spaces/spaces_selection·ts - Spaces app Spaces Spaces Data displays separate data for each space in a custom space

[kibanamachine]

A test failed on a tracked branch

Error: retry.try timeout: TimeoutError: Waiting for element to be located By(css selector, a[href="#/dashboards"])
Wait timed out after 10011ms
    at /dev/shm/workspace/kibana/node_modules/selenium-webdriver/lib/webdriver.js:841:17
    at process._tickCallback (internal/process/next_tick.js:68:7)
    at onFailure (/dev/shm/workspace/kibana/test/common/services/retry/retry_for_success.ts:28:9)
    at retryForSuccess (/dev/shm/workspace/kibana/test/common/services/retry/retry_for_success.ts:68:13)

First failure: Jenkins Build

[elasticmachine]

Pinging @elastic/kibana-test-triage (failed-test)

[kibanamachine]

New failure: Jenkins Build

[tylersmalley]

Issue hasn't been occurred in quite some time, closing.

[kibanamachine]

New failure: Jenkins Build

[spalger]

This hasn't failed for over a month and then in the last 24 hours has failed 4 PRs and now master:

PRs were all against master, doesn't seem to have spread to other branches yet, but I have a feeling if @elastic/kibana-security doesn't take a look at this quick then a backport will be merged that causes the flakiness to spread to other branches.

skipped

master: fcbcc63
7.x/7.9: 6c1250f

[legrego]

Note for future us: Looks like we have no index patterns in the custom space. Maybe the request to add sample data failed, aborted, or was undone somehow? We shouldn't be been redirected to the index pattern management screen, because index patterns should exist at this point in the test.

[kibanamachine]

New failure: Jenkins Build

[kibanamachine]

New failure: Jenkins Build

[kibanamachine]

New failure: Jenkins Build

[kibanamachine]

New failure: Jenkins Build

[spalger]

Looks like the backport went in... skipping in 7.x too