-
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: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/lens/open_in_lens/tsvb/dashboard·ts - lens app - TSVB Open in Lens Dashboard to TSVB to Lens should convert a by reference TSVB viz to a Lens viz #179307
Comments
Pinging @elastic/kibana-visualizations (Team:Visualizations) |
Closing as is the first time it fails |
New failure: CI Build - main |
New failure: CI Build - main |
New failure: CI Build - main |
Skipped. main: 13dfd58 |
## Summary Fixes #179307 and speeds up a bit the `resetPage` method when possible via click on the `Visualize list` navigation breadcrumb on the top left: <img width="289" alt="Screenshot 2024-04-04 at 09 56 37" src="https://github.com/elastic/kibana/assets/924948/74011b51-34b1-4cfa-a78e-4224a3494a25"> The work on `navigateToNewVisualization` (function called by `resetPage`) had some side effects for some tests where a uiSettings changes were used as shortcut for the time picker: in such case a `forceRefresh` option has been provided now to cover it, but I may suggest to reduce the usage as much as possible. The new change lead to an average of ~5 minutes saving only within the `open_in_lens/tsvb` test suite, but it is a rough number as the average between the savings on the CI on the flaky runner. Probably there's an extra saving on other test suites as well. Flaky runner for the `Open in Lens/TSVB` test suite (50x runs): https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5604 Flaky runner for the `Lens - Group5` test suite (50x runs): https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5606#_ ### 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
New failure: CI Build - main |
Closing for now, but will check again after another failure. |
New failure: CI Build - main |
New failure: CI Build - main |
## Summary Fixes elastic#190227 Fixes elastic#190737 elastic#190990 elastic#190802 elastic#179307 (couldn't find the rootcause so just decided to align the solution with other files that follow similar path and are not flaky) Fixes elastic#191151 elastic#191152 elastic#191176 elastic#191177 elastic#191178 elastic#191153 elastic#191238 Fixes elastic#190711 (cherry picked from commit 2a033c1)
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-elasticsearch-snapshot-verify - main |
New failure: kibana-elasticsearch-snapshot-verify - main |
Skipped. main: 40fa231 |
## Summary Fixes: #190737, #190802, #190990, #179307 This test started failing after @nreese Reset PR was merged here: #201687 and the Lens embeddable refactor PR introducing a regression which affected the test. Later on the PR was reverted with #201902 . ### 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
closed in #202275 |
…2275) ## Summary Fixes: elastic#190737, elastic#190802, elastic#190990, elastic#179307 This test started failing after @nreese Reset PR was merged here: elastic#201687 and the Lens embeddable refactor PR introducing a regression which affected the test. Later on the PR was reverted with elastic#201902 . ### 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
A test failed on a tracked branchFirst failure: CI Build - main
The current since 2024-11-29 error is not anymore the one shown above, but:
The text was updated successfully, but these errors were encountered: