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/apps/monitoring/cluster/overview·js - Monitoring app Cluster overview for Green cluster with Gold license shows elasticsearch panel with data #71796

Closed
kibanamachine opened this issue Jul 15, 2020 · 16 comments · Fixed by #71812
Labels
blocker failed-test A test failure on a tracked branch, potentially flaky-test skipped-test Team:Monitoring Stack Monitoring team v7.9.0 v8.0.0

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Jul 15, 2020

A test failed on a tracked branch

{ TimeoutError: Waiting for element to be located By(css selector, [data-test-subj="clusterItemContainerElasticsearch"] [data-test-subj="statusIcon"])
Wait timed out after 10049ms
    at /dev/shm/workspace/kibana/node_modules/selenium-webdriver/lib/webdriver.js:842:17
    at process._tickCallback (internal/process/next_tick.js:68:7) name: 'TimeoutError', remoteStacktrace: '' }

First failure: Jenkins Build

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Jul 15, 2020
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@elasticmachine
Copy link
Contributor

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

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@tylersmalley tylersmalley added the Team:Monitoring Stack Monitoring team label Jul 15, 2020
@elasticmachine
Copy link
Contributor

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

@tylersmalley
Copy link
Contributor

Test was consistently failing in master - Skipped and marked as a 7.9 blocker:

main/8.0: a851325
7.x/7.9: 8305e62

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@sgrodzicki sgrodzicki added this to the Stack Monitoring UI 7.9 milestone Jul 15, 2020
@tylersmalley
Copy link
Contributor

I believe this to be caused by #71337, which I have reverted in master.

@tylersmalley
Copy link
Contributor

Testing restoring the skipped suite here: #71812

@sgrodzicki sgrodzicki linked a pull request Jul 15, 2020 that will close this issue
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:Monitoring Stack Monitoring team v7.9.0 v8.0.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants