-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
[Uptime] Fix flaky snapshot count test by adding timeout for required element #54839
[Uptime] Fix flaky snapshot count test by adding timeout for required element #54839
Conversation
Pinging @elastic/kibana-test-triage (failed-test) |
Pinging @elastic/uptime (Team:uptime) |
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.
LGTM WFG. Let's run this a second time after it goes green just in case. No rush here.
@elasticmachine merge upstream |
user doesn't have permission to update head repository |
Looks like we got a failure from an unrelated test. |
@elasticmachine merge upstream |
user doesn't have permission to update head repository |
@elasticmachine merge upstream |
user doesn't have permission to update head repository |
048c04c
to
fabf96d
Compare
@elasticmachine merge upstream |
user doesn't have permission to update head repository |
@elasticmachine merge upstream |
user doesn't have permission to update head repository |
@spalger is there a way I can get this PR to merge upstream so I don't have to manually merge master every time I want to re-run it? |
@elasticmachine merge upstream |
user doesn't have permission to update head repository |
fabf96d
to
17367c1
Compare
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
#56065 fixed the test that this was aimed at solving. |
Summary
Fixes #54527.
This test was failing periodically because we were applying filters to our application state and expecting the data displayed to be present. At times this takes longer to render than what we were seeing in our local environments. This PR adds a
retry
block to those tests in an effort to ensure that the page has adequate time to re-render with the updated data.Checklist
Use
strikethroughsto remove checklist items you don't feel are applicable to this PR.For maintainers