-
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
Failing test: Jest Integration Tests.x-pack/plugins/security_solution/server/integration_tests - telemetry tasks telemetry-prebuilt-rule-alerts should manage runtime errors searching endpoint metrics #188234
Comments
Pinging @elastic/security-solution (Team: SecuritySolution) |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
/skip |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
skipped in: #188313 |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - 8.15 |
New failure: kibana-on-merge - 8.15 |
## Summary Re: elastic#188234 (cherry picked from commit d5345e4)
# Backport This will backport the following commits from `main` to `8.15`: - [[ci] skip flaky test (#188313)](#188313) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Alex Szabo","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-07-15T14:33:15Z","message":"[ci] skip flaky test (#188313)\n\n## Summary\r\nRe: https://github.com/elastic/kibana/issues/188234","sha":"d5345e442dce28b0ee5ef057988b156ba78784ad","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","skip-ci","backport:prev-minor","v8.16.0"],"title":"[ci] skip flaky test","number":188313,"url":"https://github.com/elastic/kibana/pull/188313","mergeCommit":{"message":"[ci] skip flaky test (#188313)\n\n## Summary\r\nRe: https://github.com/elastic/kibana/issues/188234","sha":"d5345e442dce28b0ee5ef057988b156ba78784ad"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/188313","number":188313,"mergeCommit":{"message":"[ci] skip flaky test (#188313)\n\n## Summary\r\nRe: https://github.com/elastic/kibana/issues/188234","sha":"d5345e442dce28b0ee5ef057988b156ba78784ad"}}]}] BACKPORT--> Co-authored-by: Alex Szabo <[email protected]>
New failure: kibana-on-merge - 8.14 |
New failure: kibana-on-merge - 8.14 |
## Summary Re: elastic#188234 (cherry picked from commit d5345e4)
New failure: kibana-on-merge - 8.15 |
New failure: kibana-on-merge - 8.15 |
New failure: kibana-on-merge - 8.14 |
New failure: kibana-on-merge - 8.14 |
## Summary Fixes: elastic#188234 elastic#187719 and elastic#178918 The flakiness was while calculating the Detection Rules task invocations. It could have two different RCs: 1) The code didn't retry in case the task wasn't executed yet, which makes sense in a CI environment, which is slower than a dev environment; 2) The timestamp to filter out requests was calculated after the task was triggered, and if the task is executed fast enough, it could lead to empty responses because of that. (cherry picked from commit 358e104)
) # Backport This will backport the following commits from `main` to `8.15`: - [[Telemetry][Security Solution] Fix flaky tests (#190044)](#190044) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sebastián Zaffarano","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-08-07T13:13:13Z","message":"[Telemetry][Security Solution] Fix flaky tests (#190044)\n\n## Summary\r\n\r\nFixes: https://github.com/elastic/kibana/issues/188234\r\nhttps://github.com/elastic/kibana/issues/187719 and\r\nhttps://github.com//issues/178918\r\n\r\nThe flakiness was while calculating the Detection Rules task\r\ninvocations. It could have two different RCs: 1) The code didn't retry\r\nin case the task wasn't executed yet, which makes sense in a CI\r\nenvironment, which is slower than a dev environment; 2) The timestamp to\r\nfilter out requests was calculated after the task was triggered, and if\r\nthe task is executed fast enough, it could lead to empty responses\r\nbecause of that.","sha":"358e104ebcc2bfcfeec3457b2e913d071d27745d","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team: SecuritySolution","v8.15.0","v8.16.0"],"title":"[Telemetry][Security Solution] Fix flaky tests","number":190044,"url":"https://github.com/elastic/kibana/pull/190044","mergeCommit":{"message":"[Telemetry][Security Solution] Fix flaky tests (#190044)\n\n## Summary\r\n\r\nFixes: https://github.com/elastic/kibana/issues/188234\r\nhttps://github.com/elastic/kibana/issues/187719 and\r\nhttps://github.com//issues/178918\r\n\r\nThe flakiness was while calculating the Detection Rules task\r\ninvocations. It could have two different RCs: 1) The code didn't retry\r\nin case the task wasn't executed yet, which makes sense in a CI\r\nenvironment, which is slower than a dev environment; 2) The timestamp to\r\nfilter out requests was calculated after the task was triggered, and if\r\nthe task is executed fast enough, it could lead to empty responses\r\nbecause of that.","sha":"358e104ebcc2bfcfeec3457b2e913d071d27745d"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/190044","number":190044,"mergeCommit":{"message":"[Telemetry][Security Solution] Fix flaky tests (#190044)\n\n## Summary\r\n\r\nFixes: https://github.com/elastic/kibana/issues/188234\r\nhttps://github.com/elastic/kibana/issues/187719 and\r\nhttps://github.com//issues/178918\r\n\r\nThe flakiness was while calculating the Detection Rules task\r\ninvocations. It could have two different RCs: 1) The code didn't retry\r\nin case the task wasn't executed yet, which makes sense in a CI\r\nenvironment, which is slower than a dev environment; 2) The timestamp to\r\nfilter out requests was calculated after the task was triggered, and if\r\nthe task is executed fast enough, it could lead to empty responses\r\nbecause of that.","sha":"358e104ebcc2bfcfeec3457b2e913d071d27745d"}}]}] BACKPORT--> Co-authored-by: Sebastián Zaffarano <[email protected]>
A test failed on a tracked branch
First failure: kibana-elasticsearch-snapshot-verify - main
The text was updated successfully, but these errors were encountered: