Open kibanamachine opened 3 years ago
Pinging @elastic/kibana-presentation (Team:Presentation)
Currently only three failures in the past week:
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
Skipped
master: e9988b1cc2c8f322f63f441891c9032c9b9f25ce 7.x: 5ed51b4e7c2f49f16d462419805993861212e836
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
Pinging @elastic/kibana-app-services (Team:AppServices)
A recent change that might have indirectly caused these failures: https://github.com/elastic/kibana/pull/104780
Looks like test failures aren't related to the search sessions, but all the tests just fail to load a flights sample dashboard. They report: "15 of 17 panels loaded".
These two panels in "no results state" are causing the problem, as they don't set a proper of data-
attributes to let test suite know that they finished loading.
I filed https://github.com/elastic/kibana/issues/106085 and as soon as this is fixed by @elastic/kibana-app , we can re-enable the test.
@wylieconlon, I am also not sure if this is a valid behaviour that those visualizations could produce a "No results" state with sample data. I assume you didn't hit this in the pr https://github.com/elastic/kibana/pull/104780 ? I am not sure if this is some kind of a race condition in lens code or if this is a valid possible behaviour with how sample data works. Do you maybe know? Otherwise, I think it worth creating an issue to investigate and make it clear?
Also a note: today the skipped test is passing, both locally and on ci: https://github.com/elastic/kibana/pull/106071#issuecomment-882486605
@Dosant Yes I think you're right that https://github.com/elastic/kibana/issues/106085 is the cause, but there's something else that's special about those two panels: they are both using the time shift feature. Could that be related, since the data for all the other panels is loaded?
Could that be related, since the data for all the other panels are loaded?
I am not sure, but an important remark is that the empty state happens not when the test tries to restore a search session, but it happens and fails on the initial dashboard load. So this could likely happen in any other test that would use sample flights data and this empty state is not related to search sessions functionality
New failure: CI Build - main
New failure: CI Build - 8.7
It looks like this is a completely different failure this time:
delayed vs 1 week earlier
and canceled vs 1 week earlier
both loaded successfully:
The element [data-test-subj="embeddableError"] was still present when it should have disappeared.
My guess is that one of the charts on this dashboard errored out, but it's difficult to tell which one at this point.
I think the next step is to replace instances of await testSubjects.missingOrFail('embeddableError');
with a method on the dashboard service that can actually report which panels have failed, then run a flaky test runner against this.
New failure: kibana-on-merge - main
A test failed on a tracked branch
First failure: Jenkins Build