Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/api_keys - API Keys app "after all" hook in "API Keys app"

[kibanamachine]

A test failed on a tracked branch

{ UnexpectedAlertOpenError: unexpected alert open: {Alert text : }
  (Session info: headless chrome=80.0.3987.149)
  (Driver info: chromedriver=80.0.3987.16 (320f6526c1632ad4f205ebce69b99a062ed78647-refs/branch-heads/3987@{#185}),platform=Linux 4.9.0-12-amd64 x86_64)
    at Object.checkLegacyResponse (/dev/shm/workspace/kibana/node_modules/selenium-webdriver/lib/error.js:592:13)
    at parseHttpResponse (/dev/shm/workspace/kibana/node_modules/selenium-webdriver/lib/http.js:554:13)
    at Executor.execute (/dev/shm/workspace/kibana/node_modules/selenium-webdriver/lib/http.js:489:26)
    at process._tickCallback (internal/process/next_tick.js:68:7)
  name: 'UnexpectedAlertOpenError',
  remoteStacktrace: '',
  text_: '' }

First failure: Jenkins Build

[elasticmachine]

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

[kibanamachine]

New failure: Jenkins Build

[kibanamachine]

New failure: Jenkins Build

[kibanamachine]

New failure: Jenkins Build

[kibanamachine]

New failure: Jenkins Build

[kibanamachine]

New failure: Jenkins Build

[tylersmalley]

@cuff-links, it looks like you recently added these tests. Would you mind looking into the flakiness?

[spalger]

Sorry, forgot to update this issue, it was caused by an alert dialog being opened after #61535, which was fixed in #61705