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 isolate 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) #145363

Closed
kibanamachine opened this issue Nov 16, 2022 · 3 comments · Fixed by #149538
Closed

Failing test: Jest Integration Tests.x-pack/plugins/security_solution/public/management/components/endpoint_responder/command_render_components/integration_tests - When using isolate 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) #145363

kibanamachine opened this issue Nov 16, 2022 · 3 comments · Fixed by #149538
Assignees
@paul-tavares
Labels
failed-test A test failure on a tracked branch, potentially flaky-test OLM Sprint Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Nov 16, 2022 •
edited
Loading

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.<anonymous> (/var/lib/buildkite-agent/builds/kb-n2-4-spot-14df00d6f8751183/elastic/kibana-on-merge/kibana/x-pack/plugins/security_solution/public/management/components/endpoint_responder/command_render_components/integration_tests/isolate_action.test.tsx:223:55)

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

New failure: CI Build - 8.6

jbudz added a commit that referenced this issue Nov 17, 2022
@jbudz
skip flaky suite. #145363
55816d9
jbudz added a commit that referenced this issue Nov 17, 2022
@jbudz
skip flaky suite. #145363
03042ac
@jbudz
Copy link
Member

jbudz commented Nov 17, 2022

Skipped

main: 55816d9
8.6: 03042ac

@kevinlog kevinlog added the v8.7.0 label Jan 5, 2023
@paul-tavares paul-tavares mentioned this issue Jan 25, 2023
Merged
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: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Security Solution][Endpoint] Re-enable FTR tests for Endpoint Responder paul-tavares/kibana
5 participants
@jbudz @elasticmachine @kibanamachine @kevinlog @paul-tavares