-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Monitoring] Handle cloud test failures #74162
[Monitoring] Handle cloud test failures #74162
Conversation
Pinging @elastic/stack-monitoring (Team:Monitoring) |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
//it moves on to the cluster overview page. | ||
await retry.try(async () => { | ||
// it moves on to the cluster overview page. | ||
await retry.tryForTime(10000, async () => { |
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.
nit: Ten seconds seems kind of long. Is there any way to add Promise.race() condition? Maybe OR if a certain element is visible?
But, I think it's still fine if not, so up to you
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.
Looks good 👍
@elasticmachine merge upstream |
💚 Build SucceededBuild metrics
History
To update your PR or re-run it, just comment with: |
Co-authored-by: Elastic Machine <[email protected]>
Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Elastic Machine <[email protected]>
Co-authored-by: Elastic Machine <[email protected]> # Conflicts: # x-pack/test/functional/apps/monitoring/time_filter.js
Co-authored-by: Elastic Machine <[email protected]> # Conflicts: # x-pack/test/functional/apps/monitoring/time_filter.js
Fixes #63055
Fixes #72191
Best way to test this is to stand up a cloud cluster and run the functional test runner against it, something like: