Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/uptime/certificates·ts - Uptime app with generated data certificates page "before each" hook for "performs search against monitor id"

[kibanamachine]

A test failed on a tracked branch

Error: retry.try timeout: Error: expected testSubject(uptimeCertificatesPage) to exist
    at TestSubjects.existOrFail (/dev/shm/workspace/kibana/test/functional/services/common/test_subjects.ts:62:15)
    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

[elasticmachine]

Pinging @elastic/uptime (Team:uptime)

[spalger]

This failed on master and 7.x pretty close to each other, hasn't failed on PRs yet. Looks like @andrewvc and @shahzad31 have modified these tests recently.

Screenshot during failure:

The test logs indicate that it was looking for the uptimeCertificatesPage element, but it kept retrying and never reclicked the uptimeCertificatesLink element, probably because the testSubjects.existOrFail() method uses a different default timeout... You might want to use config.get('timeouts.waitForExists') as the timeout for this call or just use the exists() method and throw your own error when it's missing.

[shahzad31]

I will take a look at this, feel free to skip them if seems obstructive.

[spalger]

I assume the new flakiness was introduced by #66806, so in the last week or so they've only failed at one point in time, so I don't feel the need to skip them. Additionally, I suspect that PR makes things more stable than they were before so I don't feel the urge to revert it.

That said, I think the flakiness is coming from a shared service so it probably means that many tests are more likely to be flaky until we get this fixed, so being quick to fix would definitely be appreciated.