-
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: X-Pack Search Sessions Integration.x-pack/test/search_sessions_integration/tests/apps/dashboard/async_search/save_search_session_relative_time·ts - Dashboard save a search sessions with relative time Saves and restores a session with relative time ranges #97701
Comments
Pinging @elastic/kibana-presentation (Team:Presentation) |
New failure: Jenkins Build |
1 similar comment
New failure: Jenkins Build |
New failure: Jenkins Build |
1 similar comment
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 |
Pinging @elastic/kibana-app-services (Team:AppServices) |
A recent change that might have indirectly caused these failures: #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 I filed #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 #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: #106071 (comment) |
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. |
New failure: CI Build - main |
New failure: CI Build - 8.7 |
Closes #97701 ## Summary This PR replaces all instances of `await testSubjects.missingOrFail('embeddableError');` with a call to the new `noErrorEmbeddablesPresent()` method from the `dashboardExpect` service. This `noErrorEmbeddablesPresent()` method adds some extra debugging logic to the error embeddable check where, if at least one error embeddable is present, then both the panel title(s) and the relevant error message(s) will be printed as part of the error that is thrown. With these changes, if the attached flaky test fails again, we should at least have some more information on **why** it failed. ### Flaky Test Runner This was specifically only running the flaky `save_search_session_relative_time.ts` test suite: <a href="https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2024"><img src="https://user-images.githubusercontent.com/8698078/227240095-a336b03b-6499-4d80-8b60-5e325d54a4ae.png"/></a> ### Checklist - [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 - [ ] 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)
…153457) Closes elastic#97701 ## Summary This PR replaces all instances of `await testSubjects.missingOrFail('embeddableError');` with a call to the new `noErrorEmbeddablesPresent()` method from the `dashboardExpect` service. This `noErrorEmbeddablesPresent()` method adds some extra debugging logic to the error embeddable check where, if at least one error embeddable is present, then both the panel title(s) and the relevant error message(s) will be printed as part of the error that is thrown. With these changes, if the attached flaky test fails again, we should at least have some more information on **why** it failed. ### Flaky Test Runner This was specifically only running the flaky `save_search_session_relative_time.ts` test suite: <a href="https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2024"><img src="https://user-images.githubusercontent.com/8698078/227240095-a336b03b-6499-4d80-8b60-5e325d54a4ae.png"/></a> ### Checklist - [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 - [ ] 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 - main |
A test failed on a tracked branch
First failure: Jenkins Build
The text was updated successfully, but these errors were encountered: