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/visualize/feature_controls/visualize_security·ts - Visualize feature controls security global visualize all privileges allow saving a currently loaded saved query as a new query via the saved query management component #56220

Closed
kibanamachine opened this issue Jan 28, 2020 · 9 comments
Closed

Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/visualize/feature_controls/visualize_security·ts - Visualize feature controls security global visualize all privileges allow saving a currently loaded saved query as a new query via the saved query management component #56220

kibanamachine opened this issue Jan 28, 2020 · 9 comments
Labels
failed-test A test failure on a tracked branch, potentially flaky-test

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Jan 28, 2020 •
edited
Loading

A test failed on a tracked branch

Error: retry.try timeout: TimeoutError: Waiting for element to be located By(css selector, [data-test-subj="saved-query-management-save-as-new-button"])
Wait timed out after 10059ms
    at /dev/shm/workspace/kibana/node_modules/selenium-webdriver/lib/webdriver.js:841:17
    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 Jan 28, 2020
@elasticmachine
Copy link
Contributor

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

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@brianseeders
Copy link
Contributor

There were some tests dependent upon another skipped test from here: #50018

@kibanamachine kibanamachine reopened this Jan 28, 2020
@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

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
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@brianseeders @elasticmachine @kibanamachine