-
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/dashboard/group2/sync_colors·ts - dashboard sync colors should be possible to disable color sync #148558
Comments
Pinging @elastic/kibana-presentation (Team:Presentation) |
New failure: CI Build - main |
…ional/apps/dashboard/group2/sync_colors·ts (#150087) Fixes #148557 and #148558 Flaky test runner https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/1854 See #148557 (comment) for explanation of failure. PR resolves flakiness by adding retry in clickCreateNewLink, ensuring clickCreateNewLink opens lens or else retries.
closed by #150087 |
…ional/apps/dashboard/group2/sync_colors·ts (elastic#150087) Fixes elastic#148557 and elastic#148558 Flaky test runner https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/1854 See elastic#148557 (comment) for explanation of failure. PR resolves flakiness by adding retry in clickCreateNewLink, ensuring clickCreateNewLink opens lens or else retries.
New failure: CI Build - main |
closing, duplicate of #148557 |
New failure: CI Build - 8.7 |
closing, duplicate of #148557 |
New failure: CI Build - 8.8 |
Looks like some sort of @elastic/kibana-visualizations Do ya'll know where this tip popover is coming from, and if there is an easy way to disable it for tests? Or perhaps this is a SharedUX thing... 👀 |
@Heenawter we are using this in Lens to indicate that there is no data for this timespan because the users were confused. It exists in unified search https://github.com/elastic/kibana/blob/main/src/plugins/unified_search/public/query_string_input/no_data_popover.tsx You can:
|
Ran the flaky test runner 100 times and was unable to reproduce this - seems like it may have been a one-off failure in 8.8 and is not on |
A test failed on a tracked branch
First failure: CI Build - main
The text was updated successfully, but these errors were encountered: