[Cloud Security] Fix flaky test#183262
Merged
CohenIdo merged 5 commits intoelastic:mainfrom May 15, 2024
Merged
Conversation
Contributor
|
Pinging @elastic/kibana-cloud-security-posture (Team:Cloud Security) |
This was
linked to
issues
May 13, 2024
Contributor
|
@CohenIdo please elaborate on the ticket's description of what stands behind this fix. This will serve us in the future as a knowledge base |
Contributor
Author
|
@elasticmachine merge upstream |
JordanSh
approved these changes
May 15, 2024
Contributor
Author
|
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Solves:
The tests mentioned above failed with the following error message:
I consulted with the fleet team and discovered that there is a task responsible for writing to the data stream named
ds-metrics-fleet_server, and it was recommended to disable this task during FTRs.After updating the test configuration to disable this task and re-enabling the previously skipped tests, I executed the tests using the flaky test runner, and it appears that this action has resolved the issue.