-
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
[Entity Analytics] MKI test failure fixes #190182
Conversation
@@ -31,7 +31,8 @@ import { REFRESH_BUTTON } from '../screens/security_header'; | |||
export const updateDashboardTimeRange = () => { | |||
// eslint-disable-next-line cypress/no-force | |||
cy.get(GET_DATE_PICKER_APPLY_BUTTON(GLOBAL_FILTERS_CONTAINER)).click({ force: true }); // Force to fix global timerange flakiness | |||
cy.get(REFRESH_BUTTON).click(); | |||
// eslint-disable-next-line cypress/no-force | |||
cy.get(REFRESH_BUTTON).click({ force: true }); // Force to fix even more global timerange flakiness |
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.
very rarely (1 in over 1000 test runs) the query button is disabled I dont understand why and I have no screenshots, but the button is not what is primarily under test so I think a force is reasonable here
@elasticmachine merge upstream |
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 changes LGTM. @hop-dev did you have a chance to run the tests against real project on QA (MKI) to confirm flakiness is fixed?
@elasticmachine merge upstream |
@dmlemeshko the issue is so rare I didn't think that would be effective, do you have a concern about the change? |
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Unknown metric groupsESLint disabled line counts
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: |
Summary
closes #10176
I've been looking into a few of our flaky tests and come up with a couple of actions, I will comment on them individually.