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: X-Pack Jest Tests.x-pack/plugins/security_solution/public/resolver/view/panels - Resolver: when analyzing a tree with only the origin and paginated related events, and when the component instance ID is resolverComponentInstanceID when the URL query string is showing a resolver with nodeID origin, panel view nodeEventsInCategory, and eventCategory registry should show the load more data button #85714

Closed
kibanamachine opened this issue Dec 13, 2020 · 5 comments · Fixed by #85994
Closed

Failing test: X-Pack Jest Tests.x-pack/plugins/security_solution/public/resolver/view/panels - Resolver: when analyzing a tree with only the origin and paginated related events, and when the component instance ID is resolverComponentInstanceID when the URL query string is showing a resolver with nodeID origin, panel view nodeEventsInCategory, and eventCategory registry should show the load more data button #85714

kibanamachine opened this issue Dec 13, 2020 · 5 comments · Fixed by #85994
Labels
blocker failed-test A test failure on a tracked branch, potentially flaky-test skipped-test Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:SIEM v7.11.0 v8.0.0

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Dec 13, 2020 •
edited
Loading

A test failed on a tracked branch

Error: thrown: "Exceeded timeout of 5000 ms for a test.
Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."
    at /dev/shm/workspace/parallel/7/kibana/x-pack/plugins/security_solution/public/resolver/view/panels/node_events_of_type.test.tsx:62:5
    at _dispatchDescribe (/dev/shm/workspace/kibana/node_modules/jest-circus/build/index.js:67:26)
    at describe (/dev/shm/workspace/kibana/node_modules/jest-circus/build/index.js:30:5)
    at /dev/shm/workspace/parallel/7/kibana/x-pack/plugins/security_solution/public/resolver/view/panels/node_events_of_type.test.tsx:53:3
    at _dispatchDescribe (/dev/shm/workspace/kibana/node_modules/jest-circus/build/index.js:67:26)
    at describe (/dev/shm/workspace/kibana/node_modules/jest-circus/build/index.js:30:5)
    at Object.<anonymous> (/dev/shm/workspace/parallel/7/kibana/x-pack/plugins/security_solution/public/resolver/view/panels/node_events_of_type.test.tsx:17:1)
    at Runtime._execModule (/dev/shm/workspace/kibana/node_modules/jest-runtime/build/index.js:1299:24)
    at Runtime._loadModule (/dev/shm/workspace/kibana/node_modules/jest-runtime/build/index.js:898:12)
    at Runtime.requireModule (/dev/shm/workspace/kibana/node_modules/jest-runtime/build/index.js:746:10)
    at jestAdapter (/dev/shm/workspace/kibana/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:106:13)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at runTestInternal (/dev/shm/workspace/kibana/node_modules/jest-runner/build/runTest.js:380:16)
    at runTest (/dev/shm/workspace/kibana/node_modules/jest-runner/build/runTest.js:472:34)
    at Object.worker (/dev/shm/workspace/kibana/node_modules/jest-runner/build/testWorker.js:133:12)

First failure: Jenkins Build
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Dec 13, 2020
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@mistic mistic added Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:SIEM labels Dec 14, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/siem (Team:SIEM)

mistic added a commit that referenced this issue Dec 14, 2020
@mistic
skip flaky suite (#85714)
b8954b6
mistic added a commit that referenced this issue Dec 14, 2020
@mistic
skip flaky suite (#85714)
bbfd613
@mistic
Copy link
Member

mistic commented Dec 14, 2020 •
edited
Loading

The test was failing both on master and 7.x and looks flaky. Skipping for now.

master: b8954b6
7.x: bbfd613

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

mistic added a commit that referenced this issue Dec 15, 2020
@mistic
skip flaky suite (#85714)
5fdace3
mistic added a commit that referenced this issue Dec 15, 2020
@mistic
skip flaky suite (#85714)
27afabd
@michaelolo24 michaelolo24 mentioned this issue Dec 15, 2020
Merged
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
blocker failed-test A test failure on a tracked branch, potentially flaky-test skipped-test Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:SIEM v7.11.0 v8.0.0
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Security Solution][Resolver] Fix failing test & cleaned up prop drilling michaelolo24/kibana
3 participants
@mistic @elasticmachine @kibanamachine