Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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 uptime alerts tls alert can open alert flyout #65948

Closed
kibanamachine opened this issue May 9, 2020 · 5 comments · Fixed by #72963
Assignees
Labels
blocker failed-test A test failure on a tracked branch, potentially flaky-test skipped-test Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability v7.8.2

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented May 9, 2020

A test failed on a tracked branch

Error: retry.try timeout: ElementClickInterceptedError: element click intercepted: Element <button class="euiContextMenuItem" type="button" aria-label="Open TLS alert flyout" data-test-subj="xpack.uptime.toggleTlsAlertFlyout">...</button> is not clickable at point (791, 243). Other element would receive the click: <div class="euiContextMenu" style="height: 135px;">...</div>
  (Session info: headless chrome=81.0.4044.122)
    at Object.throwDecodedError (/dev/shm/workspace/kibana/node_modules/selenium-webdriver/lib/error.js:550:15)
    at parseHttpResponse (/dev/shm/workspace/kibana/node_modules/selenium-webdriver/lib/http.js:565:13)
    at Executor.execute (/dev/shm/workspace/kibana/node_modules/selenium-webdriver/lib/http.js:491:26)
    at process._tickCallback (internal/process/next_tick.js:68:7)
    at onFailure (/dev/shm/workspace/kibana/test/common/services/retry/retry_for_success.ts:28:9)
    at retryForSuccess (/dev/shm/workspace/kibana/test/common/services/retry/retry_for_success.ts:68:13)

First failure: Jenkins Build

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label May 9, 2020
@elasticmachine
Copy link
Contributor

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

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@spalger spalger added the Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability label May 13, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/uptime (Team:uptime)

spalger added a commit that referenced this issue May 13, 2020
spalger added a commit that referenced this issue May 13, 2020
(cherry picked from commit 6695b18)
@spalger
Copy link
Contributor

spalger commented May 13, 2020

11 failures in the last 7 days, across master, 7.x, and PRs across both branches

image

Skipped

master: 6695b18
7.x/7.9: 76e47a1
7.8: b1466c6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocker failed-test A test failure on a tracked branch, potentially flaky-test skipped-test Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability v7.8.2
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants