-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Functional Tests] Unskip tsvb timeseries test #73011
[Functional Tests] Unskip tsvb timeseries test #73011
Conversation
Pinging @elastic/kibana-test-triage (failed-test) |
Pinging @elastic/kibana-app (Team:KibanaApp) |
💚 Build SucceededBuild metrics
History
To update your PR or re-run it, just comment with: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool! ❤️
It's a known issue with the stale element reference
if a component was updated after it was found via selenium. This should definitely resolve the flakiness! Thanks!
LGTM
* [Functional Tests] Unskip tsvb timeseries test * Add retry to dropdown selection when element is not found to headless mode
* [Functional Tests] Unskip tsvb timeseries test * Add retry to dropdown selection when element is not found to headless mode
Summary
This test was skipped during this PR #33558. I managed to reproduce the flakiness locally when I run the suite on headless mode. The error was
StaleElementReferenceError: stale element reference: element is not attached to the page document
. The problem was with the From Dropdown (screenshot below). The option couldn't be found so I added a retry which seems to solve the problem.With the current solution, the flakiness is not reproducible locally, on cloud and on the flaky server (100 times) https://kibana-ci.elastic.co/job/kibana+flaky-test-suite-runner/650/
Checklist