[ML] Single metric viewer functional test: add retry to reduce flakiness

[alvarezmelissa87]

Summary

Fixes #188493

This PR unskips the single metric viewer functional test that is failing (confirmed functionality is working as expected) and increases the retries to reduce flakiness.

Flaky test runner: https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/6593

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• Flaky Test Runner was used on any tests changed
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

[elasticmachine]

Pinging @elastic/ml-ui (:ml)

[kibanamachine]

Flaky Test Runner Stats

🟠 Some tests failed. - kibana-flaky-test-suite-runner#6581

[❌] x-pack/test/functional/apps/ml/anomaly_detection_integrations/config.ts: 9/35 tests passed.

see run history

[kibanamachine]

Flaky Test Runner Stats

🟠 Some tests failed. - kibana-flaky-test-suite-runner#6586

[❌] x-pack/test/functional/apps/ml/anomaly_detection_integrations/config.ts: 9/35 tests passed.

see run history

[peteharverson]

LGTM

[pheyos]

Quick nit on the format: we tend to only change the first factor and leave the * 1000 so it's easier to see at glance how many seconds this timeout is.

[pheyos]

From the failure screenshot it looks like the click didn't have an effect (might have been triggered too early) and the click should be retried. However looking into the test log, I can see that this existOrFail times out after 120 seconds and since the wrapping retry is on a shorter time out, it leaves the retry immediately and never actually triggers the click again.
I'd propose to give the existOrFail an explicit timeout (as much as we think makes sense for going to the dashboard page, e.g. 10 seconds) and then extend the wrapping retry so it actually gives it a few tries, something like this:

    async ensureAnomalyActionDiscoverButtonClicked() {
      await retry.tryForTime(30 * 1000, async () => {
        await testSubjects.click('mlAnomaliesListRowAction_viewInDiscoverButton');
        await testSubjects.existOrFail('discoverLayoutResizableContainer', { timeout: 10 * 1000 });
      });
    },

[kibanamachine]

Flaky Test Runner Stats

🎉 All tests passed! - kibana-flaky-test-suite-runner#6593

[✅] x-pack/test/functional/apps/ml/anomaly_detection_integrations/config.ts: 30/30 tests passed.

see run history

[peteharverson]

Latest changes LGTM

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 940df01

Failed CI Steps

• Jest Tests #7
• FTR Configs #15

Test Failures

• [job] [logs] Jest Tests #7 / Template fields renders template fields with existing value

Metrics [docs]

✅ unchanged

History

• 💚 Build #222488 succeeded 07bc19d
• 💛 Build #222455 was flaky 77cb5ae

cc @alvarezmelissa87