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: Firefox XPack UI Functional Tests.x-pack/test/functional/apps/machine_learning/anomaly_detection/saved_search_job·ts - machine learning anomaly detection saved search job creation with filter and lucene query loads the job management page #49315

Closed
kibanamachine opened this issue Oct 25, 2019 · 1 comment · Fixed by #50132
Assignees
Labels
failed-test A test failure on a tracked branch, potentially flaky-test

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="mlMainTab anomalyDetection"])
Wait timed out after 10014ms
    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 lastError (/dev/shm/workspace/kibana/test/common/services/retry/retry_for_success.ts:28:9)
    at onFailure (/dev/shm/workspace/kibana/test/common/services/retry/retry_for_success.ts:68:13)
    at lastError (/dev/shm/workspace/kibana/test/common/services/retry/retry_for_success.ts:28:9)
    at onFailure (/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 Oct 25, 2019
@elasticmachine
Copy link
Contributor

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

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

Successfully merging a pull request may close this issue.

3 participants