A test failed on a tracked branch
Error: retry.try timeout: Error: retry.try timeout: TimeoutError: Waiting for element to be located By(css selector, [data-test-subj="createVisualizationPromptButton"])
Wait timed out after 10015ms
at /dev/shm/workspace/kibana/node_modules/selenium-webdriver/lib/webdriver.js:842:17
at process._tickCallback (internal/process/next_tick.js:68:7)
at onFailure (test/common/services/retry/retry_for_success.ts:28:9)
at retryForSuccess (test/common/services/retry/retry_for_success.ts:68:13)
at onFailure (test/common/services/retry/retry_for_success.ts:28:9)
at retryForSuccess (test/common/services/retry/retry_for_success.ts:68:13)
First failure: Jenkins Build

Pinging @elastic/kibana-test-triage (failed-test)
Pinging @elastic/kibana-app (Team:KibanaApp)
This test looks generally flaky, but might be particularly flaky due to firefox issues recently. I suspect the solution is a retry.
Probably related to #71979
@dej611 I think that #72882 closes this right?
Probably related to #71979
refers mostly to the bug that can be reproduced with the artificial environment with Firefox, so unfortunately not. The bug fixed in #72882 is different from the one detected here.
There are no logs available (last occurrence happened 16 of July) but the problem in code is the same as here: https://github.com/elastic/kibana/pull/71226 - so it should be fixed. Kudos to @stratoula 馃憦
Most helpful comment
There are no logs available (last occurrence happened 16 of July) but the problem in code is the same as here: https://github.com/elastic/kibana/pull/71226 - so it should be fixed. Kudos to @stratoula 馃憦