-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Comments
Pinging @elastic/response-ops (Team:ResponseOps) |
Pinging @elastic/response-ops-cases (Feature:Cases) |
New failure: CI Build - main |
New failure: CI Build - main |
Skipped main: 105138c |
New failure: CI Build - main |
## 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)
New failure: CI Build - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - 8.x |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - 8.x |
New failure: kibana-on-merge - 8.x |
New failure: kibana-on-merge - 8.x |
A test failed on a tracked branch
First failure: CI Build - main
The text was updated successfully, but these errors were encountered: