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.

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 ES Promotion: x-pack/plugins/security_solution/public/cases/components/create.Create case Step 2 - Connector Fields should change from none to Jira connector fields #84145

Closed
mistic opened this issue Nov 23, 2020 · 7 comments
Assignees
Labels
failed-es-promotion Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:SIEM

Comments

@mistic
Copy link
Member

mistic commented Nov 23, 2020

This failure is preventing the promotion of the current Elasticsearch nightly snapshot.

For more information on the Elasticsearch snapshot promotion process: https://www.elastic.co/guide/en/kibana/master/development-es-snapshots.html

Stacktrace
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 forEach (/dev/shm/workspace/kibana/x-pack/plugins/security_solution/public/cases/components/create/index.test.tsx:204:7)
    at Array.forEach (<anonymous>)
    at /dev/shm/workspace/kibana/x-pack/plugins/security_solution/public/cases/components/create/index.test.tsx:203:20
    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/kibana/x-pack/plugins/security_solution/public/cases/components/create/index.test.tsx:185: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/kibana/x-pack/plugins/security_solution/public/cases/components/create/index.test.tsx:93: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:97: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)
18:16:20  A worker process has failed to exit gracefully and has been force exited. This is likely caused by tests leaking due to improper teardown. Try running with --detectOpenHandles to find leaks.
18:16:20  Summary of all failing tests
18:16:20   FAIL  x-pack/plugins/security_solution/public/cases/components/create/index.test.tsx (25.28 s)
18:16:20    ● Create case › Step 2 - Connector Fields › should change from none to Jira connector fields
18:16:20  
18:16:20      thrown: "Exceeded timeout of 5000 ms for a test.
18:16:20      Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."
18:16:20  
18:16:20        202 |     ];
18:16:20        203 |     connectorTypes.forEach(({ label, testId, dataTestSubj }) => {
18:16:20      > 204 |       it(`should change from none to ${label} connector fields`, async () => {
18:16:20            |       ^
18:16:20        205 |         useConnectorsMock.mockReturnValue({
18:16:20        206 |           ...sampleConnectorData,
18:16:20        207 |           connectors: connectorsMock,
18:16:20  
18:16:20        at forEach (x-pack/plugins/security_solution/public/cases/components/create/index.test.tsx:204:7)
18:16:20            at Array.forEach (<anonymous>)
18:16:20        at x-pack/plugins/security_solution/public/cases/components/create/index.test.tsx:203:20
18:16:20        at x-pack/plugins/security_solution/public/cases/components/create/index.test.tsx:185:3
18:16:20        at Object.<anonymous> (x-pack/plugins/security_solution/public/cases/components/create/index.test.tsx:93:1)
18:16:20  
18:16:20  
18:16:20  Test Suites: 1 failed, 4 skipped, 3110 passed, 3111 of 3115 total
18:16:20  Tests:       1 failed, 62 skipped, 2 todo, 22459 passed, 22524 total
18:16:20  Snapshots:   3379 passed, 3379 total
18:16:20  Time:        3063.112 s
@mistic mistic added blocker Team:SIEM v8.0.0 skipped-test failed-es-promotion Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. labels Nov 23, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/siem (Team:SIEM)

mistic added a commit that referenced this issue Nov 23, 2020
@mistic
Copy link
Member Author

mistic commented Nov 23, 2020

Skipped in order to unblock the snapshot.

master/8.0: f4de383

@MindyRS MindyRS added the Team:Detections and Resp Security Detection Response Team label Mar 15, 2022
@elasticmachine
Copy link
Contributor

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

@e40pud e40pud self-assigned this Jul 13, 2023
@e40pud
Copy link
Contributor

e40pud commented Jul 14, 2023

Checking this test, I found that it was removed completely in this commit more than 2 years ago as part of this PR.

@yctercero @MadameSheema do you think we should just close this ticket?

@yctercero
Copy link
Contributor

I think it's fine to close out given the test was removed.

@MadameSheema
Copy link
Member

I think it's fine to close out given the test was removed.

Agree :)

@e40pud
Copy link
Contributor

e40pud commented Jul 17, 2023

Closing per above comments

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
failed-es-promotion Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:SIEM
Projects
None yet
Development

No branches or pull requests

7 participants