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: Jest Integration Tests.x-pack/plugins/security_solution/public/management/components/endpoint_responder/command_render_components/integration_tests - When using processes action from response actions console and when console is closed (not terminated) and then reopened should display completion output if done (no additional API calls) #146692

Open
kibanamachine opened this issue Nov 30, 2022 · 6 comments
Open

Failing test: Jest Integration Tests.x-pack/plugins/security_solution/public/management/components/endpoint_responder/command_render_components/integration_tests - When using processes action from response actions console and when console is closed (not terminated) and then reopened should display completion output if done (no additional API calls) #146692

kibanamachine opened this issue Nov 30, 2022 · 6 comments
Assignees
@paul-tavares
Labels
failed-test A test failure on a tracked branch, potentially flaky-test OLM Sprint Team:Defend Workflows “EDR Workflows” sub-team of Security Solution Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Nov 30, 2022 •
edited

A test failed on a tracked branch

Error: expect(jest.fn()).toHaveBeenCalledTimes(expected)

Expected number of calls: 1
Received number of calls: 2
    at Object.toHaveBeenCalledTimes (/var/lib/buildkite-agent/builds/kb-n2-4-spot-98a8daca0f37e73a/elastic/kibana-on-merge/kibana/x-pack/plugins/security_solution/public/management/components/endpoint_responder/command_render_components/integration_tests/get_processes_action.test.tsx:216:55)

First failure: CI Build - main
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Nov 30, 2022
@botelastic botelastic bot added the needs-team Issues missing a team label label Nov 30, 2022
@kibanamachine kibanamachine added the Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. label Nov 30, 2022
@elasticmachine
Copy link
Contributor

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

@botelastic botelastic bot removed the needs-team Issues missing a team label label Nov 30, 2022
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kevinlog kevinlog added the Team:Defend Workflows “EDR Workflows” sub-team of Security Solution label Feb 21, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-defend-workflows (Team:Defend Workflows)

@kevinlog
Copy link
Contributor

@paul-tavares can you take a look?

@paul-tavares
Copy link
Contributor

I reviewed the code that handles this, which is also used by every other response action we execute from the console, and it all looks as I would have expected it. I also ran this test suite 50 times locally (on a loop) and got no failures. Perhaps this is a fluke? 🤷‍♂

Closing for now.

Output of 50 runs of this one test file:

Image

@kibanamachine kibanamachine reopened this Feb 27, 2024
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

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

@paul-tavares paul-tavares

Labels
failed-test A test failure on a tracked branch, potentially flaky-test OLM Sprint Team:Defend Workflows “EDR Workflows” sub-team of Security Solution Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@elasticmachine @kibanamachine @kevinlog @paul-tavares