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 Plugin Functional Tests.x-pack/test/plugin_functional/test_suites/resolver - Resolver embeddable test app "before each" hook for "renders a container div for the embeddable" #60190

Closed
kibanamachine opened this issue Mar 14, 2020 · 3 comments
Closed

Failing test: Chrome X-Pack UI Plugin Functional Tests.x-pack/test/plugin_functional/test_suites/resolver - Resolver embeddable test app "before each" hook for "renders a container div for the embeddable" #60190

kibanamachine opened this issue Mar 14, 2020 · 3 comments
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@kibanamachine
Copy link
Contributor

A test failed on a tracked branch

Error: retry.tryForTime timeout: Error: retry.try timeout: TimeoutError: Waiting for element to be located By(css selector, [data-test-subj="kibanaChrome"])
Wait timed out after 61212ms
    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)
    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 Mar 14, 2020
@elasticmachine
Copy link
Contributor

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

@spalger
Copy link
Contributor

spalger commented Mar 14, 2020 •
edited
Loading

This is caused by the same bug that @mattkime tried to fix in #60168, as was suggested by @streamich we should probably move over VALUE_CLICK_TRIGGER and APPLY_FILTER_TRIGGER too. Tracking this in #60148

@spalger spalger added the Team:Visualizations Visualization editors, elastic-charts and infrastructure label Mar 14, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app (Team:KibanaApp)

@spalger spalger closed this as completed Mar 14, 2020
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:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Milestone
No milestone
Development

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