[ResponseOps] Fix embeddable alerts panel flaky tests#227999
[ResponseOps] Fix embeddable alerts panel flaky tests#227999cnasikas merged 35 commits intoelastic:mainfrom
Conversation
Flaky Test Runner Stats🎉 All tests passed! - kibana-flaky-test-suite-runner#8652[✅] x-pack/platform/test/functional_with_es_ssl/apps/embeddable_alerts_table/config.ts: 200/200 tests passed. |
Flaky Test Runner Stats🎉 All tests passed! - kibana-flaky-test-suite-runner#8668[✅] x-pack/platform/test/functional_with_es_ssl/apps/embeddable_alerts_table/config.ts: 200/200 tests passed. |
|
Pinging @elastic/response-ops (Team:ResponseOps) |
Flaky Test Runner Stats🟠 Some tests failed. - kibana-flaky-test-suite-runner#8673[❌] x-pack/platform/test/functional_with_es_ssl/apps/embeddable_alerts_table/config.ts: 0/200 tests passed. |
Flaky Test Runner Stats🟠 Some tests failed. - kibana-flaky-test-suite-runner#8895[❌] x-pack/platform/test/alerting_api_integration/security_and_spaces/group3/config.ts: 0/200 tests passed. |
Flaky Test Runner Stats🎉 All tests passed! - kibana-flaky-test-suite-runner#9654[✅] x-pack/platform/test/functional_with_es_ssl/apps/embeddable_alerts_table/config.ts: 200/200 tests passed. |
|
Starting backport for target branches: 8.19, 9.1, 9.2 https://github.com/elastic/kibana/actions/runs/18904466326 |
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Async chunks
History
cc @cnasikas |
## Summary Another attempt to fix the flaky tests with the embeddable alerts panel. The issue is that alerts are not being generated. I made the rules more sensitive so they will always produce alerts and use the event log to check the rules' execution status. I run the flaky test runner 3 x 200 without any issues. Fixes: elastic#227748 Fixes: elastic#220807 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> (cherry picked from commit 3cb9979)
💔 Some backports could not be created
Note: Successful backport PRs will be merged automatically after passing CI. Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
…#241100) # Backport This will backport the following commits from `main` to `9.2`: - [[ResponseOps] Fix embeddable alerts panel flaky tests (#227999)](#227999) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Christos Nasikas","email":"christos.nasikas@elastic.co"},"sourceCommit":{"committedDate":"2025-10-29T10:17:04Z","message":"[ResponseOps] Fix embeddable alerts panel flaky tests (#227999)\n\n## Summary\n\nAnother attempt to fix the flaky tests with the embeddable alerts panel.\nThe issue is that alerts are not being generated. I made the rules more\nsensitive so they will always produce alerts and use the event log to\ncheck the rules' execution status. I run the flaky test runner 3 x 200\nwithout any issues.\n\nFixes: https://github.com/elastic/kibana/issues/227748\nFixes: https://github.com/elastic/kibana/issues/220807\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"3cb997977f9fe132c44de0216455852e8340f42e","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","Team:obs-ux-management","backport:version","v9.3.0","v8.19.7","v9.1.7","v9.2.1"],"title":"[ResponseOps] Fix embeddable alerts panel flaky tests","number":227999,"url":"https://github.com/elastic/kibana/pull/227999","mergeCommit":{"message":"[ResponseOps] Fix embeddable alerts panel flaky tests (#227999)\n\n## Summary\n\nAnother attempt to fix the flaky tests with the embeddable alerts panel.\nThe issue is that alerts are not being generated. I made the rules more\nsensitive so they will always produce alerts and use the event log to\ncheck the rules' execution status. I run the flaky test runner 3 x 200\nwithout any issues.\n\nFixes: https://github.com/elastic/kibana/issues/227748\nFixes: https://github.com/elastic/kibana/issues/220807\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"3cb997977f9fe132c44de0216455852e8340f42e"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.1","9.2"],"targetPullRequestStates":[{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/227999","number":227999,"mergeCommit":{"message":"[ResponseOps] Fix embeddable alerts panel flaky tests (#227999)\n\n## Summary\n\nAnother attempt to fix the flaky tests with the embeddable alerts panel.\nThe issue is that alerts are not being generated. I made the rules more\nsensitive so they will always produce alerts and use the event log to\ncheck the rules' execution status. I run the flaky test runner 3 x 200\nwithout any issues.\n\nFixes: https://github.com/elastic/kibana/issues/227748\nFixes: https://github.com/elastic/kibana/issues/220807\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"3cb997977f9fe132c44de0216455852e8340f42e"}},{"branch":"8.19","label":"v8.19.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.1","label":"v9.1.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.2","label":"v9.2.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Christos Nasikas <christos.nasikas@elastic.co>
## Summary Another attempt to fix the flaky tests with the embeddable alerts panel. The issue is that alerts are not being generated. I made the rules more sensitive so they will always produce alerts and use the event log to check the rules' execution status. I run the flaky test runner 3 x 200 without any issues. Fixes: elastic#227748 Fixes: elastic#220807 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
## Summary Another attempt to fix the flaky tests with the embeddable alerts panel. The issue is that alerts are not being generated. I made the rules more sensitive so they will always produce alerts and use the event log to check the rules' execution status. I run the flaky test runner 3 x 200 without any issues. Fixes: elastic#227748 Fixes: elastic#220807 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> (cherry picked from commit 3cb9979) # Conflicts: # x-pack/platform/test/functional_with_es_ssl/apps/embeddable_alerts_table/embeddable_alerts_table.ts # x-pack/platform/test/functional_with_es_ssl/plugins/alerts/tsconfig.json
## Summary Another attempt to fix the flaky tests with the embeddable alerts panel. The issue is that alerts are not being generated. I made the rules more sensitive so they will always produce alerts and use the event log to check the rules' execution status. I run the flaky test runner 3 x 200 without any issues. Fixes: elastic#227748 Fixes: elastic#220807 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
## Summary Another attempt to fix the flaky tests with the embeddable alerts panel. The issue is that alerts are not being generated. I made the rules more sensitive so they will always produce alerts and use the event log to check the rules' execution status. I run the flaky test runner 3 x 200 without any issues. Fixes: elastic#227748 Fixes: elastic#220807 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
…#241154) # Backport This will backport the following commits from `main` to `9.1`: - [[ResponseOps] Fix embeddable alerts panel flaky tests (#227999)](#227999) <!--- Backport version: 10.1.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Christos Nasikas","email":"christos.nasikas@elastic.co"},"sourceCommit":{"committedDate":"2025-10-29T10:17:04Z","message":"[ResponseOps] Fix embeddable alerts panel flaky tests (#227999)\n\n## Summary\n\nAnother attempt to fix the flaky tests with the embeddable alerts panel.\nThe issue is that alerts are not being generated. I made the rules more\nsensitive so they will always produce alerts and use the event log to\ncheck the rules' execution status. I run the flaky test runner 3 x 200\nwithout any issues.\n\nFixes: https://github.com/elastic/kibana/issues/227748\nFixes: https://github.com/elastic/kibana/issues/220807\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"3cb997977f9fe132c44de0216455852e8340f42e","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","Team:obs-ux-management","backport:version","v9.3.0","v8.19.7","v9.1.7","v9.2.1"],"title":"[ResponseOps] Fix embeddable alerts panel flaky tests","number":227999,"url":"https://github.com/elastic/kibana/pull/227999","mergeCommit":{"message":"[ResponseOps] Fix embeddable alerts panel flaky tests (#227999)\n\n## Summary\n\nAnother attempt to fix the flaky tests with the embeddable alerts panel.\nThe issue is that alerts are not being generated. I made the rules more\nsensitive so they will always produce alerts and use the event log to\ncheck the rules' execution status. I run the flaky test runner 3 x 200\nwithout any issues.\n\nFixes: https://github.com/elastic/kibana/issues/227748\nFixes: https://github.com/elastic/kibana/issues/220807\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"3cb997977f9fe132c44de0216455852e8340f42e"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.1"],"targetPullRequestStates":[{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/227999","number":227999,"mergeCommit":{"message":"[ResponseOps] Fix embeddable alerts panel flaky tests (#227999)\n\n## Summary\n\nAnother attempt to fix the flaky tests with the embeddable alerts panel.\nThe issue is that alerts are not being generated. I made the rules more\nsensitive so they will always produce alerts and use the event log to\ncheck the rules' execution status. I run the flaky test runner 3 x 200\nwithout any issues.\n\nFixes: https://github.com/elastic/kibana/issues/227748\nFixes: https://github.com/elastic/kibana/issues/220807\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"3cb997977f9fe132c44de0216455852e8340f42e"}},{"branch":"8.19","label":"v8.19.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.1","label":"v9.1.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.2","label":"v9.2.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/241100","number":241100,"state":"MERGED","mergeCommit":{"sha":"0679d9c9347d54986cd26c8c6e79914e6cfa7f93","message":"[9.2] [ResponseOps] Fix embeddable alerts panel flaky tests (#227999) (#241100)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.2`:\n- [[ResponseOps] Fix embeddable alerts panel flaky tests\n(#227999)](https://github.com/elastic/kibana/pull/227999)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Christos Nasikas <christos.nasikas@elastic.co>"}}]}] BACKPORT--> --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
#241155) # Backport This will backport the following commits from `main` to `8.19`: - [[ResponseOps] Fix embeddable alerts panel flaky tests (#227999)](#227999) <!--- Backport version: 10.1.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Christos Nasikas","email":"christos.nasikas@elastic.co"},"sourceCommit":{"committedDate":"2025-10-29T10:17:04Z","message":"[ResponseOps] Fix embeddable alerts panel flaky tests (#227999)\n\n## Summary\n\nAnother attempt to fix the flaky tests with the embeddable alerts panel.\nThe issue is that alerts are not being generated. I made the rules more\nsensitive so they will always produce alerts and use the event log to\ncheck the rules' execution status. I run the flaky test runner 3 x 200\nwithout any issues.\n\nFixes: https://github.com/elastic/kibana/issues/227748\nFixes: https://github.com/elastic/kibana/issues/220807\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"3cb997977f9fe132c44de0216455852e8340f42e","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","Team:obs-ux-management","backport:version","v9.3.0","v8.19.7","v9.1.7","v9.2.1"],"title":"[ResponseOps] Fix embeddable alerts panel flaky tests","number":227999,"url":"https://github.com/elastic/kibana/pull/227999","mergeCommit":{"message":"[ResponseOps] Fix embeddable alerts panel flaky tests (#227999)\n\n## Summary\n\nAnother attempt to fix the flaky tests with the embeddable alerts panel.\nThe issue is that alerts are not being generated. I made the rules more\nsensitive so they will always produce alerts and use the event log to\ncheck the rules' execution status. I run the flaky test runner 3 x 200\nwithout any issues.\n\nFixes: https://github.com/elastic/kibana/issues/227748\nFixes: https://github.com/elastic/kibana/issues/220807\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"3cb997977f9fe132c44de0216455852e8340f42e"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.1"],"targetPullRequestStates":[{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/227999","number":227999,"mergeCommit":{"message":"[ResponseOps] Fix embeddable alerts panel flaky tests (#227999)\n\n## Summary\n\nAnother attempt to fix the flaky tests with the embeddable alerts panel.\nThe issue is that alerts are not being generated. I made the rules more\nsensitive so they will always produce alerts and use the event log to\ncheck the rules' execution status. I run the flaky test runner 3 x 200\nwithout any issues.\n\nFixes: https://github.com/elastic/kibana/issues/227748\nFixes: https://github.com/elastic/kibana/issues/220807\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"3cb997977f9fe132c44de0216455852e8340f42e"}},{"branch":"8.19","label":"v8.19.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.1","label":"v9.1.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.2","label":"v9.2.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/241100","number":241100,"state":"MERGED","mergeCommit":{"sha":"0679d9c9347d54986cd26c8c6e79914e6cfa7f93","message":"[9.2] [ResponseOps] Fix embeddable alerts panel flaky tests (#227999) (#241100)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.2`:\n- [[ResponseOps] Fix embeddable alerts panel flaky tests\n(#227999)](https://github.com/elastic/kibana/pull/227999)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Christos Nasikas <christos.nasikas@elastic.co>"}}]}] BACKPORT--> --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
## Summary Another attempt to fix the flaky tests with the embeddable alerts panel. The issue is that alerts are not being generated. I made the rules more sensitive so they will always produce alerts and use the event log to check the rules' execution status. I run the flaky test runner 3 x 200 without any issues. Fixes: elastic#227748 Fixes: elastic#220807 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Summary
Another attempt to fix the flaky tests with the embeddable alerts panel. The issue is that alerts are not being generated. I made the rules more sensitive so they will always produce alerts and use the event log to check the rules' execution status. I run the flaky test runner 3 x 200 without any issues.
Fixes: #227748
Fixes: #220807
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.