Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[8.12] [Security Solution][Detection Engine] fixes flaky ES|QL tests (#…
…173251) (#174099) # Backport This will backport the following commits from `main` to `8.12`: - [[Security Solution][Detection Engine] fixes flaky ES|QL tests (#173251)](#173251) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Vitalii Dmyterko","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-01-02T16:00:08Z","message":"[Security Solution][Detection Engine] fixes flaky ES|QL tests (#173251)\n\n## Summary\r\n\r\n- fixes flaky ES|QL tests\r\nhttps://github.com//issues/173006\r\n- the reason is an issue in cypress itself\r\nhttps://github.com/cypress-io/cypress/issues/22113. It doesn't have a\r\nfix yet, but I tried some suggested workaround, as calling\r\n`uncaught:exception` handler after page is opened, so it is registered\r\nin the same origin. Which seemed to help, since there was no failures in\r\n300 runs. Usual rate of flakiness before the fix was 3-7 failures per\r\n100 runs. Hopefully, it will work and we won't see any errors in future.\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- 100 runs for all Detection tests:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/4625\r\n- 2 x 100 for just failing ones:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/4620,\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/4605\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <[email protected]>","sha":"b365051dc24156d810004917efa64dbcbaa64a59","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detections and Resp","Team: SecuritySolution","backport:prev-minor","Team:Detection Engine","v8.12.0","v8.13.0"],"title":"[Security Solution][Detection Engine] fixes flaky ES|QL tests","number":173251,"url":"https://github.com/elastic/kibana/pull/173251","mergeCommit":{"message":"[Security Solution][Detection Engine] fixes flaky ES|QL tests (#173251)\n\n## Summary\r\n\r\n- fixes flaky ES|QL tests\r\nhttps://github.com//issues/173006\r\n- the reason is an issue in cypress itself\r\nhttps://github.com/cypress-io/cypress/issues/22113. It doesn't have a\r\nfix yet, but I tried some suggested workaround, as calling\r\n`uncaught:exception` handler after page is opened, so it is registered\r\nin the same origin. Which seemed to help, since there was no failures in\r\n300 runs. Usual rate of flakiness before the fix was 3-7 failures per\r\n100 runs. Hopefully, it will work and we won't see any errors in future.\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- 100 runs for all Detection tests:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/4625\r\n- 2 x 100 for just failing ones:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/4620,\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/4605\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <[email protected]>","sha":"b365051dc24156d810004917efa64dbcbaa64a59"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"8.12","label":"v8.12.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.13.0","branchLabelMappingKey":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/173251","number":173251,"mergeCommit":{"message":"[Security Solution][Detection Engine] fixes flaky ES|QL tests (#173251)\n\n## Summary\r\n\r\n- fixes flaky ES|QL tests\r\nhttps://github.com//issues/173006\r\n- the reason is an issue in cypress itself\r\nhttps://github.com/cypress-io/cypress/issues/22113. It doesn't have a\r\nfix yet, but I tried some suggested workaround, as calling\r\n`uncaught:exception` handler after page is opened, so it is registered\r\nin the same origin. Which seemed to help, since there was no failures in\r\n300 runs. Usual rate of flakiness before the fix was 3-7 failures per\r\n100 runs. Hopefully, it will work and we won't see any errors in future.\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- 100 runs for all Detection tests:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/4625\r\n- 2 x 100 for just failing ones:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/4620,\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/4605\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <[email protected]>","sha":"b365051dc24156d810004917efa64dbcbaa64a59"}}]}] BACKPORT--> Co-authored-by: Vitalii Dmyterko <[email protected]>
- Loading branch information