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.

Sign up for GitHub

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

Jump to bottom

Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/monitoring/kibana/instance·js - Monitoring app Kibana instance detail "before all" hook for "should have Instance Summary Status showing correct info" #53159

Closed
kibanamachine opened this issue Dec 16, 2019 · 4 comments · Fixed by #81200
Closed

Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/monitoring/kibana/instance·js - Monitoring app Kibana instance detail "before all" hook for "should have Instance Summary Status showing correct info" #53159

kibanamachine opened this issue Dec 16, 2019 · 4 comments · Fixed by #81200
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Monitoring Stack Monitoring team

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Dec 16, 2019 •
edited
Loading

A test failed on a tracked branch

Error: retry.tryForTime timeout: Error: retry.try timeout: Error: App failed to load: login in 10000ms appUrl=http://localhost:6121/login currentUrl=http://localhost:6121/app/kibana#/home
    at retry.try (/dev/shm/workspace/kibana/test/functional/page_objects/common_page.ts:250:19)
    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)
    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 Dec 16, 2019
@elasticmachine
Copy link
Contributor

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

@tylersmalley
Copy link
Contributor

Issue hasn't been occurred in quite some time, closing.

@kibanamachine kibanamachine reopened this Oct 21, 2020
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@mistic mistic added the Team:Monitoring Stack Monitoring team label Oct 21, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/stack-monitoring (Team:Monitoring)

@chrisronline chrisronline mentioned this issue Oct 21, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Monitoring Stack Monitoring team
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Monitoring] Use async/await chrisronline/kibana
4 participants
@tylersmalley @mistic @elasticmachine @kibanamachine