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 test: Jest Tests.x-pack/plugins/cases/public/components/custom_fields/text - Configure renders correctly #176600

Open
kibanamachine opened this issue Feb 9, 2024 · 16 comments · Fixed by #177590
Assignees
Labels
blocker failed-test A test failure on a tracked branch, potentially flaky-test Feature:Cases Cases feature skipped-test Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v9.0.0

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Feb 9, 2024

A test failed on a tracked branch

Error: thrown: "Exceeded timeout of 5000 ms for a test.
Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout."
    at it (/var/lib/buildkite-agent/builds/kb-n2-4-spot-e0da57fde629e472/elastic/kibana-on-merge/kibana/x-pack/plugins/cases/public/components/custom_fields/text/configure.test.tsx:22:3)
    at _dispatchDescribe (/var/lib/buildkite-agent/builds/kb-n2-4-spot-e0da57fde629e472/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/index.js:91:26)
    at describe (/var/lib/buildkite-agent/builds/kb-n2-4-spot-e0da57fde629e472/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/index.js:55:5)
    at Object.describe (/var/lib/buildkite-agent/builds/kb-n2-4-spot-e0da57fde629e472/elastic/kibana-on-merge/kibana/x-pack/plugins/cases/public/components/custom_fields/text/configure.test.tsx:15:1)
    at Runtime._execModule (/var/lib/buildkite-agent/builds/kb-n2-4-spot-e0da57fde629e472/elastic/kibana-on-merge/kibana/node_modules/jest-runtime/build/index.js:1430:24)
    at Runtime._loadModule (/var/lib/buildkite-agent/builds/kb-n2-4-spot-e0da57fde629e472/elastic/kibana-on-merge/kibana/node_modules/jest-runtime/build/index.js:1013:12)
    at Runtime.requireModule (/var/lib/buildkite-agent/builds/kb-n2-4-spot-e0da57fde629e472/elastic/kibana-on-merge/kibana/node_modules/jest-runtime/build/index.js:873:12)
    at jestAdapter (/var/lib/buildkite-agent/builds/kb-n2-4-spot-e0da57fde629e472/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:77:13)
    at runTestInternal (/var/lib/buildkite-agent/builds/kb-n2-4-spot-e0da57fde629e472/elastic/kibana-on-merge/kibana/node_modules/jest-runner/build/runTest.js:367:16)
    at runTest (/var/lib/buildkite-agent/builds/kb-n2-4-spot-e0da57fde629e472/elastic/kibana-on-merge/kibana/node_modules/jest-runner/build/runTest.js:444:34)

First failure: CI Build - main

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Feb 9, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Feb 9, 2024
@kibanamachine kibanamachine added the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Feb 9, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Feb 9, 2024
@cnasikas cnasikas added the Feature:Cases Cases feature label Feb 9, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops-cases (Feature:Cases)

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

jbudz added a commit that referenced this issue Feb 12, 2024
@jbudz
Copy link
Member

jbudz commented Feb 12, 2024

Skipped

main: 105138c

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

fkanout pushed a commit to fkanout/kibana that referenced this issue Mar 4, 2024
fkanout pushed a commit to fkanout/kibana that referenced this issue Mar 4, 2024
## Summary

PR elastic#176863 improved the cases
context provided which we assumed caused some flakiness in our tests. I
am unskipping a couple of tests to test if the changes on that PR
stabilized the tests.

Fixes elastic#176805
Fixes elastic#174528
Fixes elastic#174527
Fixes elastic#174526
Fixes elastic#174525
Fixes elastic#176600
Fixes elastic#146394


### Checklist

Delete any items that are not applicable to this PR.

- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios

### For maintainers

- [x] This was checked for breaking API changes and was [labeled
appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - 8.x

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@jbudz
Copy link
Member

jbudz commented Sep 26, 2024

Skipped

main: 34cb733
8.x/8.16: 2eba4b5

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - 8.x

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - 8.x

@cnasikas cnasikas removed the v8.16.0 label Oct 29, 2024
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - 8.x

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocker failed-test A test failure on a tracked branch, potentially flaky-test Feature:Cases Cases feature skipped-test Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v9.0.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants