-
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/case_view/components - Case View Page files tab should render the custom fields correctly #185046
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 |
@elastic/response-ops could someone take a look at this test, or increase the timeout on it if it's warranted? |
New failure: kibana-on-merge - main |
Skipped. main: 339be82 |
New failure: kibana-on-merge - main |
Fixed by #191212 |
New failure: kibana-on-merge - 8.x |
New failure: kibana-on-merge - 8.x |
New failure: kibana-on-merge - 8.x |
New failure: kibana-on-merge - 8.x |
New failure: kibana-on-merge - 8.x |
New failure: kibana-on-merge - 8.x |
New failure: kibana-on-merge - 8.x |
New failure: kibana-on-merge - 8.x |
New failure: kibana-on-merge - 8.x |
New failure: kibana-on-merge - 8.x |
New failure: kibana-on-merge - 8.x |
Skipped |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
I left the 8.16.0 label off, I'm assuming it was triaged as non-blocker. It is still skipped on that branch. |
A test failed on a tracked branch
First failure: kibana-on-merge - main
The text was updated successfully, but these errors were encountered: