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: UI Functional Tests.test/functional/apps/visualize/_pie_chart·js - visualize app pie chart empty time window should show no data message when no data on selected timerange #29373

Closed
kibanamachine opened this issue Jan 25, 2019 · 4 comments · Fixed by #29903
Closed

Failing test: UI Functional Tests.test/functional/apps/visualize/_pie_chart·js - visualize app pie chart empty time window should show no data message when no data on selected timerange #29373

kibanamachine opened this issue Jan 25, 2019 · 4 comments · Fixed by #29903
Labels
failed-test A test failure on a tracked branch, potentially flaky-test PR sent

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Jan 25, 2019 •
edited
Loading

A test failed on a tracked branch


        Error: retry.try timeout: Error: expected 10 to equal 11
    at Assertion.assert (node_modules/expect.js/index.js:96:13)
    at Assertion.be.Assertion.equal (node_modules/expect.js/index.js:216:10)
    at Assertion.(anonymous function) [as be] (node_modules/expect.js/index.js:69:24)
    at retry.try (test/functional/page_objects/visualize_page.js:938:42)
    at process._tickCallback (internal/process/next_tick.js:68:7)
    at lastError (test/common/services/retry/retry_for_success.js:29:9)
    at retryForSuccess (test/common/services/retry/retry_for_success.js:63:13)

First failure: Jenkins Build
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Jan 25, 2019
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@spalger
Copy link
Contributor

spalger commented Feb 2, 2019

The filter is being sent, but only part of it is getting into the input box and the vis editor ignores the error:
image

Related #29900

@spalger spalger mentioned this issue Feb 2, 2019
Merged
@spalger spalger added the PR sent label Feb 2, 2019
spalger pushed a commit that referenced this issue Feb 2, 2019
[pageObjects/visualize] use testSubjects.setValue() to avoid partial …
32190e3 
…input (#29903)

Fixes #29373
Fixes #29833

This flaky test is caused by the filter input box not being filled in completely. I was able to reproduce this once locally, but only after running the tests a couple times. To fix this I tried switching to the `testSubjects.setValue()` function, which focuses the input and clears its value before attempting to type into the field. This seems to have a higher success rate as I was able to run the test 40 times after making the change without a failure.
spalger pushed a commit to spalger/kibana that referenced this issue Feb 2, 2019
[pageObjects/visualize] use testSubjects.setValue() to avoid partial …
eedc09d 
…input (elastic#29903)

Fixes elastic#29373
Fixes elastic#29833

This flaky test is caused by the filter input box not being filled in completely. I was able to reproduce this once locally, but only after running the tests a couple times. To fix this I tried switching to the `testSubjects.setValue()` function, which focuses the input and clears its value before attempting to type into the field. This seems to have a higher success rate as I was able to run the test 40 times after making the change without a failure.
spalger pushed a commit that referenced this issue Feb 3, 2019
[pageObjects/visualize] use testSubjects.setValue() to avoid partial …
7bd3137 
…input (#29903) (#29904)

Fixes #29373
Fixes #29833

This flaky test is caused by the filter input box not being filled in completely. I was able to reproduce this once locally, but only after running the tests a couple times. To fix this I tried switching to the `testSubjects.setValue()` function, which focuses the input and clears its value before attempting to type into the field. This seems to have a higher success rate as I was able to run the test 40 times after making the change without a failure.
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 PR sent
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[pageObjects/visualize] use testSubjects.setValue() to avoid partial input spalger/kibana
2 participants
@spalger @kibanamachine