Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional_with_es_ssl/apps/triggers_actions_ui/alert_create_flyout·ts - Actions and Triggers app create alert should successfully test valid es_query alert

[kibanamachine]

A test failed on a tracked branch

TimeoutError: The element [data-test-subj="testQuerySuccess"] was still present when it should have disappeared.
Wait timed out after 2690ms
    at /var/lib/buildkite-agent/builds/kb-cigroup-6-6f608bd28ef6a7b7/elastic/kibana-daily/kibana/node_modules/selenium-webdriver/lib/webdriver.js:842:17
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:95:5) {
  remoteStacktrace: ''
}

First failure: CI Build

[kibanamachine]

New failure: CI Build

[kibanamachine]

New failure: CI Build

[kibanamachine]

New failure: CI Build

[kibanamachine]

New failure: CI Build

[kibanamachine]

New failure: CI Build

[jbudz]

skipped

main: 94bbeec
7.x: 0d76f6b
7.15: 5cc6d0d

[elasticmachine]

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

[kibanamachine]

New failure: CI Build

[gmmorris]

@ymao1 - was this moved back to triage on purpose?

[ymao1]

It was in triage and I thought it was related to another flaky test I was working on so I assigned myself but it is not

[mikecote]

Assigned to @ymao1 to see if another PR will cause this flaky test to go away when unskipped.

[kibanamachine]

New failure: CI Build

[kibanamachine]

New failure: CI Build

[kibanamachine]

New failure: CI Build

[jbudz]

skipped

main: 6ad596f
7.x: ea7ce5c

[ymao1]

This test needs to be tested using the buildkite flaky test runner, not the jenkins one. There are timing differences in how the 2 CI systems run and the flakiness does not show up in the jenkins flaky test runner.

[ymao1]

From Spencer on Slack:

Looking at the test and the logs (which are admittedly harder to see in Buildkite for the time being, fix imminent) it seems that the // Invalid query portion of the test is executing before the success toast from the previous execution has cleared. This is why the speed of Buildkite is causing this test to fail more frequently than on Jenkins. I'd recommend adding a await testSubjects.waitForDeleted('testQuerySuccess'); between the two sections of the test