-
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/files - FilesUtilityBar renders correctly #174571
Comments
Pinging @elastic/response-ops (Team:ResponseOps) |
Pinging @elastic/response-ops-cases (Feature:Cases) |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
Skipped. main: 42010e3 |
## Summary I changed the testing providers to use the new theme provider just in case the old providers were a cause of flakiness. I also mocked the hooks used by the `AddFile` component as the tests for it are not flaky. Fixes: #174571 ### 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: kibana-on-merge - 8.15 |
New failure: kibana-on-merge - 8.15 |
New failure: kibana-on-merge - 8.15 |
New failure: kibana-on-merge - 8.15 |
A test failed on a tracked branch
First failure: CI Build - main
The text was updated successfully, but these errors were encountered: