Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Failing test: Security Solution Cypress.x-pack/test/security_solution_cypress/cypress/e2e/detection_response/rule_management/related_integrations/related_integrations·cy·ts - Related integrations related Integrations Advanced Setting is disabled rules management table should not display a badge with the installed integrations should not display a badge with the installed integrations #173306

Closed
Tracked by #173731
kibanamachine opened this issue Dec 13, 2023 · 14 comments
Closed
Tracked by #173731

Failing test: Security Solution Cypress.x-pack/test/security_solution_cypress/cypress/e2e/detection_response/rule_management/related_integrations/related_integrations·cy·ts - Related integrations related Integrations Advanced Setting is disabled rules management table should not display a badge with the installed integrations should not display a badge with the installed integrations #173306

kibanamachine opened this issue Dec 13, 2023 · 14 comments
Assignees
@jpdjere
Labels
8.12 candidate failed-test A test failure on a tracked branch, potentially flaky-test Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Dec 13, 2023 •
edited
Loading

A test failed on a tracked branch

AssertionError: Timed out retrying after 150000ms: expected '[ <a.euiLink.css-10d78p6-euiLink-primary>, 19 more... ]' to have text 'Prebuilt rule with related integrations', but the text was 'Container Workload ProtectionEndpoint SecurityAbnormal Process ID or Lock File CreatedLinux Restricted Shell Breakout via Linux Binary(s)UAC Bypass Attempt via Windows Directory MasqueradingSuspicious File Creation in /etc for PersistenceUnusual File Creation - Alternate Data StreamPotential Persistence Through Run Control DetectedHigh Number of Process TerminationsInteractive Terminal Spawned via PythonPowerShell Keylogging ScriptPersistence via Update Orchestrator Service HijackPotential Linux Ransomware Note Creation DetectedModification of Dynamic Linker Preload Shared ObjectEnumeration of Privileged Local Groups MembershipPotential Credential Access via Windows UtilitiesRemote System Discovery CommandsThird-party Backup Files Deleted via Unexpected ProcessUAC Bypass via Windows Firewall Snap-In HijackNew Systemd Service Created by Previously Unknown Process'
    at Context.eval (webpack:///./e2e/detection_response/rule_management/related_integrations/related_integrations.cy.ts:250:26)

First failure: CI Build - main
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Dec 13, 2023
@botelastic botelastic bot added the needs-team Issues missing a team label label Dec 13, 2023
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@MadameSheema MadameSheema added triage_needed Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Detection Rule Management Security Detection Rule Management Team labels Dec 13, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detections-response (Team:Detections and Resp)

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Dec 13, 2023
@MindyRS
Copy link

MindyRS commented Dec 13, 2023

@banderror the CODEOWNERS file missed this one too

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

mistic added a commit that referenced this issue Dec 13, 2023
@mistic
skip flaky suite (#173306)
51212f4
@mistic
Copy link
Member

mistic commented Dec 13, 2023

Skipped.

main: 51212f4

@banderror banderror assigned jpdjere and unassigned banderror Dec 14, 2023
@banderror
Copy link
Contributor

@banderror the CODEOWNERS file missed this one too

@MindyRS Looking into it.

@banderror banderror mentioned this issue Dec 20, 2023
Closed
@banderror
Copy link
Contributor

The test has been fixed and unskipped in main and 8.12.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jpdjere jpdjere

Labels
8.12 candidate failed-test A test failure on a tracked branch, potentially flaky-test Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@MindyRS @mistic @jpdjere @banderror @elasticmachine @MadameSheema @kibanamachine