Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional_with_es_ssl/apps/uptime/alert_flyout·ts - Uptime app with real-world data overview page alert flyout controls posts an alert, verfies its presence, and deletes the alert

[kibanamachine]

A test failed on a tracked branch

Error: expected 53 to equal 3
    at Assertion.assert (/dev/shm/workspace/kibana/packages/kbn-expect/expect.js:100:11)
    at Assertion.be.Assertion.equal (/dev/shm/workspace/kibana/packages/kbn-expect/expect.js:227:8)
    at Assertion.be (/dev/shm/workspace/kibana/packages/kbn-expect/expect.js:69:22)
    at Context.it (test/functional_with_es_ssl/apps/uptime/alert_flyout.ts:64:27)

First failure: Jenkins Build

[elasticmachine]

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

[elasticmachine]

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

[spalger]

Currently not failing a lot but with the spike in alerting test failures recently I'm worried...

[kibanamachine]

New failure: Jenkins Build

[kibanamachine]

New failure: Jenkins Build

[kibanamachine]

New failure: Jenkins Build

[elasticmachine]

Pinging @elastic/uptime (Team:uptime)

[justinkambic]

@brianseeders has recently updated this test to make it more resilient, but it seems even more work may be needed. Will try to investigate soon.

[mikecote]

@justinkambic We're having similar issues in the alerting functional tests, I'm working on a PR here (#62817) and was hoping to fix Uptime with it. It seems it may be a different issue, possibly something like #63224 but I haven't had time to investigate yet either.

[shahzad31]

seems to have been resolved.