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 UI Functional Tests.test/functional/apps/discover/_discover_histogram·js - discover app discover histogram should visualize weekly data with within DST changes #64083

Closed
kibanamachine opened this issue Apr 21, 2020 · 4 comments · Fixed by #72235
Assignees
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

kibanamachine commented Apr 21, 2020

A test failed on a tracked branch

{ ElementNotInteractableError: element not interactable: Element is not currently visible and may not be manipulated
  (Session info: headless chrome=81.0.4044.113)
    at Object.throwDecodedError (node_modules/selenium-webdriver/lib/error.js:550:15)
    at parseHttpResponse (node_modules/selenium-webdriver/lib/http.js:563:13)
    at Executor.execute (node_modules/selenium-webdriver/lib/http.js:489:26)
    at process._tickCallback (internal/process/next_tick.js:68:7)
  name: 'ElementNotInteractableError',
  remoteStacktrace: '#0 0x555df070c5b9 <unknown>\n' }

First failure: Jenkins Build

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

New failure: Jenkins Build

@elasticmachine
Copy link
Contributor

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

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

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

@spalger
Copy link
Contributor

spalger commented Apr 21, 2020

I'm guessing these 7.6 failures are caused by the skips you put in place @brianseeders

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 Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants