-
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
Removed delete confirmation timeout to avoid flaky failing because deletion to be a little slower on CI #77963
Removed delete confirmation timeout to avoid flaky failing because deletion to be a little slower on CI #77963
Conversation
…letion to be a little slower on CI
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
…o the loading state
💚 Build SucceededBuild metricsasync chunks size
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.
code LGTM; did this get run through the flaky test runner yet?
@pmuellr , Yes this is the results: |
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 👍
await testSubjects.missingOrFail('deleteIdsConfirmation', { timeout: 5000 }); | ||
await testSubjects.missingOrFail('deleteIdsConfirmation'); | ||
|
||
await pageObjects.common.closeToast(); | ||
await retry.try(async () => { | ||
const toastTitle = await pageObjects.common.closeToast(); | ||
expect(toastTitle).to.eql('Deleted 10 alerts'); | ||
}); |
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.
Seems much more reliable!
Good change 👍
…letion to be a little slower on CI (elastic#77963) * Removed delete confirmation timeout to avoid flaky failing because deletion to be a little slower on CI * Changed delete flow to close confim dialog immediately and set data to the loading state
Resolve #77401