-
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
[Archive Migration] kibana_sample_data_flights_index_pattern #127230
Conversation
@elasticmachine merge upstream |
Pinging @elastic/kibana-qa (Team:QA) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for fixing this test @LeeDr!
So the warning
is expected because the Input Controls don't communicate their data views back to the query bar. What is interesting to me, though, is that the test used to work with the actual values rather than warning. This is interesting because this behaviour hasn't changed at all since the Input Controls were created.
This makes me think that the flights
demo data used to be the default data view, but now it is not. When the Input Control is created against the default data view, the pills it applies work correctly without the warning. Can you think of any reason why the flights
data isn't default anymore? Should we change it so it is default for these tests?
💛 Build succeeded, but was flakyTest Failures
Metrics [docs]
History
To update your PR or re-run it, just comment with: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes LGTM! Code only review
* mostly fixed, but shows warning * Fix test, but accept Warnings in filters * remove superuser role from debugging * Remove unneeded comment * set default data view and expect actual results Co-authored-by: Kibana Machine <[email protected]> (cherry picked from commit de29e5a)
💔 Some backports could not be created
Manual backportTo create the backport manually run:
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
…#127230) * mostly fixed, but shows warning * Fix test, but accept Warnings in filters * remove superuser role from debugging * Remove unneeded comment * set default data view and expect actual results Co-authored-by: Kibana Machine <[email protected]>
Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync. |
Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync. |
4 similar comments
Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync. |
Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync. |
Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync. |
Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync. |
Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync. |
Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync. |
1 similar comment
Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync. |
I removed the |
Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync. |
Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync. |
Summary
Unskip and Migrate from
'test/functional/fixtures/es_archiver/kibana_sample_data_flights_index_pattern'
to'test/functional/fixtures/kbn_archiver/kibana_sample_data_flights_index_pattern'
2 issues with this test;
Warning
. I changed the tests to accept that for now. The other option is to then add the controls to a dashboard, with another visualizations I think, and then it would actually show the values. I haven't done that yet. Need input from the Visualization team.