-
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
[Defend Workflows] Fix artifact entries list FTR #189961
[Defend Workflows] Fix artifact entries list FTR #189961
Conversation
/ci |
b4212a1
to
7a12578
Compare
/ci |
1 similar comment
/ci |
special run: runs 3 times, but in the modified test, 3 solutions are performed 100 times each |
Flaky Test Runner Stats🟠 Some tests failed. - kibana-flaky-test-suite-runner#6741[❌] x-pack/test/security_solution_endpoint/configs/integrations.config.ts: 0/3 tests passed. |
Flaky Test Runner Stats🟠 Some tests failed. - kibana-flaky-test-suite-runner#6744[❌] x-pack/test/security_solution_endpoint/configs/integrations.config.ts: 0/3 tests passed. |
Flaky Test Runner Stats🟠 Some tests failed. - kibana-flaky-test-suite-runner#6747[❌] x-pack/test/security_solution_endpoint/configs/integrations.config.ts: 0/1 tests passed. |
08310d3
to
d39dbbf
Compare
/ci |
Flaky Test Runner Stats🟠 Some tests failed. - kibana-flaky-test-suite-runner#6748[❌] x-pack/test/security_solution_endpoint/configs/integrations.config.ts: 0/1 tests passed. |
/ci |
/ci |
Flaky Test Runner Stats🎉 All tests passed! - kibana-flaky-test-suite-runner#6772[✅] x-pack/test/security_solution_endpoint/configs/integrations.config.ts: 50/50 tests passed. |
This reverts commit e0858a5.
Pinging @elastic/security-defend-workflows (Team:Defend Workflows) |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
## Summary reducing potential flakyness in cypress tests handling event filters, by applying same change as #189961: enter text instead of selecting from dropdown > [!note] > revert da247c5 before merge - done ✅ flaky runner: https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/6782 ✅
@elasticmachine merge upstream |
@elasticmachine merge upstream |
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]
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.
LGTM 👍
Summary
tl;wr;
Note
FTRs needs to be re-enabled before merge, revert this e0858a5 - done ✅
This PR attempts to decrease flakiness in
artifact_entries_list
FTR. Looks like the reason for flakiness was the dropdown for the field to be filtered. After spending a bit of a time looking at the code, couldn't find any quick solution why it can be flaky, so instead just tried to improve the tests. For that, added a 'special' (aka hack) test case to just try to set event filter 100 times, and also a failing test case just to receive logs (77455d7) - that's why all flaky runners are red, you need to see the logs.It didn't work to add some waits to let React re-render and let the API call for suggestions be finished, didn't work to select from dropdown by text instead of test id, didn't work to add even more wait in between multiple user actions. See logs here and search for
results are in
inside the logs: https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/6744#019145e0-445d-4978-89c8-701908e14e3fIn the end, looks like the solution is simply
input
the values instead of selecting them from the dropdown. In the last hacky-flaky run, it passed all 100 times: https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/6756And a last flaky run without the hack, with the official flaky runner: https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/6772 100/100 ✅
Also, entries for the update/delete test cases are created via API call instead of UI interaction, so those cases overlap less with the create test case.