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 overview page alert flyout controls posts an alert, verifies its presence, and deletes the alert #88177

Closed
kibanamachine opened this issue Jan 13, 2021 · 15 comments · Fixed by #91455, #101562 or #130059
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability test-plan-skip

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Jan 13, 2021

A test failed on a tracked branch

Error: retry.tryForTime timeout: Error: expected [] to have a length of 1 but got 0
    at Assertion.assert (/dev/shm/workspace/parallel/5/kibana/packages/kbn-expect/expect.js:100:11)
    at Assertion.length (/dev/shm/workspace/parallel/5/kibana/packages/kbn-expect/expect.js:374:8)
    at /dev/shm/workspace/parallel/5/kibana/x-pack/test/functional_with_es_ssl/apps/uptime/alert_flyout.ts:96:46
    at runAttempt (/dev/shm/workspace/parallel/5/kibana/test/common/services/retry/retry_for_success.ts:38:15)
    at retryForSuccess (/dev/shm/workspace/parallel/5/kibana/test/common/services/retry/retry_for_success.ts:77:21)
    at Retry.tryForTime (/dev/shm/workspace/parallel/5/kibana/test/common/services/retry/retry.ts:34:14)
    at Context.<anonymous> (test/functional_with_es_ssl/apps/uptime/alert_flyout.ts:91:9)
    at Object.apply (/dev/shm/workspace/parallel/5/kibana/packages/kbn-test/src/functional_test_runner/lib/mocha/wrap_function.js:84:16)
    at onFailure (/dev/shm/workspace/parallel/5/kibana/test/common/services/retry/retry_for_success.ts:28:9)
    at retryForSuccess (/dev/shm/workspace/parallel/5/kibana/test/common/services/retry/retry_for_success.ts:68:13)
    at Retry.tryForTime (/dev/shm/workspace/parallel/5/kibana/test/common/services/retry/retry.ts:34:14)
    at Context.<anonymous> (test/functional_with_es_ssl/apps/uptime/alert_flyout.ts:91:9)
    at Object.apply (/dev/shm/workspace/parallel/5/kibana/packages/kbn-test/src/functional_test_runner/lib/mocha/wrap_function.js:84:16)

First failure: Jenkins Build

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Jan 13, 2021
@mistic mistic added the Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability label Jan 13, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/uptime (Team:uptime)

spalger added a commit that referenced this issue Jan 13, 2021

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
spalger added a commit that referenced this issue Jan 13, 2021
(cherry picked from commit 3953f96)
@spalger
Copy link
Contributor

spalger commented Jan 13, 2021

In the last 24 hours this has failed 4 PRs and now master. Not seeing anything obviously in common between the PRs, but two are on 7.x. Skipping

image

master: 3953f96
7.x/7.12: bd2941d

@justinkambic
Copy link
Contributor

justinkambic commented Feb 10, 2021

I'm thinking we can safely remove the blocker label. I tested this feature locally on master and it is working, the test is only skipped due to flakiness, which we should resolve ASAP.

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@zube zube bot added [zube]: Inbox and removed [zube]: Done labels Feb 19, 2021
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 7.16

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 7.16

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@mistic
Copy link
Member

mistic commented Nov 29, 2021

This test keeps failing and looks flaky. Skipping for now.

main/8.1: 1b3112e
8.0: 72359d3
7.16: be84f2b

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