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/graph/graph·ts - graph app graph should create new Graph workspace #45322

Closed
kibanamachine opened this issue Sep 11, 2019 · 2 comments · Fixed by #47053
Assignees
Labels
failed-test A test failure on a tracked branch, potentially flaky-test skipped-test

Comments

@kibanamachine
Copy link
Contributor

A test failed on a tracked branch


        Error: retry.try timeout: TimeoutError: Waiting for element to be located By(css selector, [data-test-subj~="confirmModalConfirmButton"])
Wait timed out after 10020ms
    at /var/lib/jenkins/workspace/elastic+kibana+master/JOB/x-pack-ciGroup1/node/linux-immutable/kibana/node_modules/selenium-webdriver/lib/webdriver.js:841:17
    at process._tickCallback (internal/process/next_tick.js:68:7)
    at lastError (/var/lib/jenkins/workspace/elastic+kibana+master/JOB/x-pack-ciGroup1/node/linux-immutable/kibana/test/common/services/retry/retry_for_success.ts:28:9)
    at onFailure (/var/lib/jenkins/workspace/elastic+kibana+master/JOB/x-pack-ciGroup1/node/linux-immutable/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 Sep 11, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-test-triage

@spalger
Copy link
Contributor

spalger commented Sep 11, 2019

Skipped by #45317

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

Successfully merging a pull request may close this issue.

4 participants