-
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: X-Pack Cloud Security Posture Functional Tests.x-pack/test/cloud_security_posture_functional/pages/cis_integrations/kspm/cis_integration_eks·ts - Cloud Security Posture Test adding Cloud Security Posture Integrations KSPM EKS KSPM EKS Shared Credentials KSPM EKS Shared Credentials Workflow #186387
Labels
8.16 candidate
automation
failed-test
A test failure on a tracked branch, potentially flaky-test
Team:Cloud Security
Cloud Security team related
Comments
kibanamachine
added
the
failed-test
A test failure on a tracked branch, potentially flaky-test
label
Jun 18, 2024
Pinging @elastic/kibana-cloud-security-posture (Team:Cloud Security) |
New failure: kibana-on-merge - main |
Skipped. main: fc6838c |
animehart
added a commit
that referenced
this issue
Jul 9, 2024
## Summary This PR is to address the following flaky FTRs #186302 #186315 #186387 #186389 The flakiness are being caused by having duplicate names for the integration when adding them. We tried adding wait before clicking on the Save button however that doesn't seem to work as it starts failing in the flaky test runner This PR gives the Integration a specific name (not relying on auto naming)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this issue
Jul 9, 2024
…#187784) ## Summary This PR is to address the following flaky FTRs elastic#186302 elastic#186315 elastic#186387 elastic#186389 The flakiness are being caused by having duplicate names for the integration when adding them. We tried adding wait before clicking on the Save button however that doesn't seem to work as it starts failing in the flaky test runner This PR gives the Integration a specific name (not relying on auto naming) (cherry picked from commit 45b0c25)
kibanamachine
added a commit
that referenced
this issue
Jul 9, 2024
…187784) (#187916) # Backport This will backport the following commits from `main` to `8.15`: - [[Cloud Security]Fix for flaky FTRs caused by duplicate names (#187784)](#187784) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Rickyanto Ang","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-07-09T20:01:00Z","message":"[Cloud Security]Fix for flaky FTRs caused by duplicate names (#187784)\n\n## Summary\r\n\r\nThis PR is to address the following flaky FTRs\r\nhttps://github.com//issues/186302\r\nhttps://github.com//issues/186315\r\nhttps://github.com//issues/186387\r\nhttps://github.com//issues/186389\r\n\r\nThe flakiness are being caused by having duplicate names for the\r\nintegration when adding them. We tried adding wait before clicking on\r\nthe Save button however that doesn't seem to work as it starts failing\r\nin the flaky test runner\r\n\r\nThis PR gives the Integration a specific name (not relying on auto\r\nnaming)","sha":"45b0c251913b6978195291a5d317972fe8c83ddb","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Cloud Security","v8.15.0","v8.16.0"],"title":"[Cloud Security]Fix for flaky FTRs caused by duplicate names","number":187784,"url":"https://github.com/elastic/kibana/pull/187784","mergeCommit":{"message":"[Cloud Security]Fix for flaky FTRs caused by duplicate names (#187784)\n\n## Summary\r\n\r\nThis PR is to address the following flaky FTRs\r\nhttps://github.com//issues/186302\r\nhttps://github.com//issues/186315\r\nhttps://github.com//issues/186387\r\nhttps://github.com//issues/186389\r\n\r\nThe flakiness are being caused by having duplicate names for the\r\nintegration when adding them. We tried adding wait before clicking on\r\nthe Save button however that doesn't seem to work as it starts failing\r\nin the flaky test runner\r\n\r\nThis PR gives the Integration a specific name (not relying on auto\r\nnaming)","sha":"45b0c251913b6978195291a5d317972fe8c83ddb"}},"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/187784","number":187784,"mergeCommit":{"message":"[Cloud Security]Fix for flaky FTRs caused by duplicate names (#187784)\n\n## Summary\r\n\r\nThis PR is to address the following flaky FTRs\r\nhttps://github.com//issues/186302\r\nhttps://github.com//issues/186315\r\nhttps://github.com//issues/186387\r\nhttps://github.com//issues/186389\r\n\r\nThe flakiness are being caused by having duplicate names for the\r\nintegration when adding them. We tried adding wait before clicking on\r\nthe Save button however that doesn't seem to work as it starts failing\r\nin the flaky test runner\r\n\r\nThis PR gives the Integration a specific name (not relying on auto\r\nnaming)","sha":"45b0c251913b6978195291a5d317972fe8c83ddb"}}]}] BACKPORT--> Co-authored-by: Rickyanto Ang <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
8.16 candidate
automation
failed-test
A test failure on a tracked branch, potentially flaky-test
Team:Cloud Security
Cloud Security team related
A test failed on a tracked branch
First failure: kibana-on-merge - main
The text was updated successfully, but these errors were encountered: