Open kibanamachine opened 5 months ago
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
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
New failure: kibana-on-merge - main
New failure: kibana-on-merge - main
New failure: kibana-on-merge - main
New failure: kibana-on-merge - main
/skip
Skipped
main: 8f9c4ab4277c0745d1185733fe1791d09dbacdba
New failure: kibana-on-merge - main
New failure: kibana-on-merge - main
New failure: kibana-on-merge - main
New failure: kibana-on-merge - main
Pinging @elastic/obs-ux-management-team (Team:obs-ux-management)
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
New failure: kibana-on-merge - main
New failure: kibana-on-merge - main
@jasonrhodes I'm in favour of removing this integration test since the API output is difficult to predict.
@jasonrhodes I'm in favour of removing this integration test since the API output is difficult to predict.
Fine by me. Are we testing this functionality in any other way, or is it just not possible to test this reliably at all, in your opinion?
We have some unit tests heavily relying on mocks
A test failed on a tracked branch
First failure: kibana-on-merge - main