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 Tests.x-pack/plugins/cases/public/components/configure_cases - ConfigureCases user interactions it show the add flyout when pressing the add connector button #116825

Closed
kibanamachine opened this issue Oct 29, 2021 · 7 comments · Fixed by #118521
Closed

Failing test: Jest Tests.x-pack/plugins/cases/public/components/configure_cases - ConfigureCases user interactions it show the add flyout when pressing the add connector button #116825

kibanamachine opened this issue Oct 29, 2021 · 7 comments · Fixed by #118521
Labels
failed-test A test failure on a tracked branch, potentially flaky-test

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Oct 29, 2021 •
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 /opt/local-ssd/buildkite/builds/kb-c2-16-c2adb3796e48b157/elastic/kibana-hourly/kibana/x-pack/plugins/cases/public/components/configure_cases/index.test.tsx:534:5
    at _dispatchDescribe (/opt/local-ssd/buildkite/builds/kb-c2-16-c2adb3796e48b157/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/index.js:67:26)
    at describe (/opt/local-ssd/buildkite/builds/kb-c2-16-c2adb3796e48b157/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/index.js:30:5)
    at /opt/local-ssd/buildkite/builds/kb-c2-16-c2adb3796e48b157/elastic/kibana-hourly/kibana/x-pack/plugins/cases/public/components/configure_cases/index.test.tsx:508:3
    at _dispatchDescribe (/opt/local-ssd/buildkite/builds/kb-c2-16-c2adb3796e48b157/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/index.js:67:26)
    at describe (/opt/local-ssd/buildkite/builds/kb-c2-16-c2adb3796e48b157/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/index.js:30:5)
    at Object.<anonymous> (/opt/local-ssd/buildkite/builds/kb-c2-16-c2adb3796e48b157/elastic/kibana-hourly/kibana/x-pack/plugins/cases/public/components/configure_cases/index.test.tsx:43:1)
    at Runtime._execModule (/opt/local-ssd/buildkite/builds/kb-c2-16-c2adb3796e48b157/elastic/kibana-hourly/kibana/node_modules/jest-runtime/build/index.js:1299:24)
    at Runtime._loadModule (/opt/local-ssd/buildkite/builds/kb-c2-16-c2adb3796e48b157/elastic/kibana-hourly/kibana/node_modules/jest-runtime/build/index.js:898:12)
    at Runtime.requireModule (/opt/local-ssd/buildkite/builds/kb-c2-16-c2adb3796e48b157/elastic/kibana-hourly/kibana/node_modules/jest-runtime/build/index.js:746:10)
    at jestAdapter (/opt/local-ssd/buildkite/builds/kb-c2-16-c2adb3796e48b157/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:106:13)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at runTestInternal (/opt/local-ssd/buildkite/builds/kb-c2-16-c2adb3796e48b157/elastic/kibana-hourly/kibana/node_modules/jest-runner/build/runTest.js:380:16)
    at runTest (/opt/local-ssd/buildkite/builds/kb-c2-16-c2adb3796e48b157/elastic/kibana-hourly/kibana/node_modules/jest-runner/build/runTest.js:472:34)
    at Object.worker (/opt/local-ssd/buildkite/builds/kb-c2-16-c2adb3796e48b157/elastic/kibana-hourly/kibana/node_modules/jest-runner/build/testWorker.js:133:12)

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

New failure: CI Build - 8.0

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-threat-hunting-cases (Team:Threat Hunting:Cases)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Nov 2, 2021
@jamster10
Copy link
Contributor

Tested locally 100 times and error did not resurface.

@spalger
Copy link
Contributor

spalger commented Nov 4, 2021

This has failed 14 times on CI in the last 7 days

image

@cnasikas
Copy link
Member

cnasikas commented Nov 4, 2021

Thank you @spalger! We stress test it locally without being able to reproduce it. Any ideas of how we can test it?

@kibanamachine kibanamachine reopened this Nov 6, 2021
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 8.0

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@cnasikas cnasikas mentioned this issue Nov 15, 2021
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
failed-test A test failure on a tracked branch, potentially flaky-test
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Cases] Fixes configuration page flaky tests cnasikas/kibana
6 participants
@spalger @cnasikas @elasticmachine @stratoula @jamster10 @kibanamachine