[Data views/Index Patterns][Scout] Fix set default data view tests#268370
Merged
Conversation
Contributor
Flaky Test Runner Stats🟠 Some tests failed. - kibana-flaky-test-suite-runner#12190[✅] src/platform/plugins/shared/data_views/test/scout/api/playwright.config.ts (--arch stateful --domain classic): 30/30 tests passed. |
Contributor
Flaky Test Runner Stats🎉 All tests passed! - kibana-flaky-test-suite-runner#12224[✅] src/platform/plugins/shared/data_views/test/scout/api/playwright.config.ts (--arch stateful --domain classic): 30/30 tests passed. |
AlexGPlay
changed the title
Contributor
Flaky Test Runner Stats🟠 Some tests failed. - kibana-flaky-test-suite-runner#12226[✅] src/platform/plugins/shared/data_views/test/scout/api/playwright.config.ts (--arch stateful --domain classic): 50/50 tests passed. |
Contributor
Author
|
The failing test in the flaky test runner failed due to an infrastructure problem, so at the test level everything looks fine |
AlexGPlay
added
release_note:skip
|
Pinging @elastic/kibana-data-discovery (Team:DataDiscovery) |
Contributor
💛 Build succeeded, but was flaky
Failed CI Steps
Test Failures
Metrics [docs]
History
cc @AlexGPlay |
davismcphee
approved these changes
May 12, 2026
Contributor
davismcphee
left a comment
davismcphee
left a comment
There was a problem hiding this comment.
Interesting issue, thanks for getting to the bottom of it!
Contributor
|
Starting backport for target branches: 9.4 |
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
May 12, 2026
…sts (#268370) (#268797) # Backport This will backport the following commits from `main` to `9.4`: - [[Data views/Index Patterns][Scout] Fix set default data view tests (#268370)](#268370) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alejandro García Parrondo","email":"31973472+AlexGPlay@users.noreply.github.com"},"sourceCommit":{"committedDate":"2026-05-12T06:47:32Z","message":"[Data views/Index Patterns][Scout] Fix set default data view tests (#268370)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/265664\nCloses https://github.com/elastic/kibana/issues/265545\nCloses https://github.com/elastic/kibana/issues/265424\nCloses https://github.com/elastic/kibana/issues/266542\nCloses https://github.com/elastic/kibana/issues/265649\nCloses https://github.com/elastic/kibana/issues/265294\n\nIt seems like many tests can run in parallel and target the same default\nindex, at the same time ES can take some time to refresh after setting\nthe new default. To fix this there are 2 main changes, the first one is\nto poll the GET endpoint until the index matches the new one that was\nset. The second change is to use a different space for each of the\nsuites so that way they are not affected by other tests.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"1b5e94e0a6ebd4182df0c830cf7320575f2b3e4e","branchLabelMapping":{"^v9.5.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:DataDiscovery","backport:version","v9.5.0","v9.4.1"],"title":"[Data views/Index Patterns][Scout] Fix set default data view tests","number":268370,"url":"https://github.com/elastic/kibana/pull/268370","mergeCommit":{"message":"[Data views/Index Patterns][Scout] Fix set default data view tests (#268370)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/265664\nCloses https://github.com/elastic/kibana/issues/265545\nCloses https://github.com/elastic/kibana/issues/265424\nCloses https://github.com/elastic/kibana/issues/266542\nCloses https://github.com/elastic/kibana/issues/265649\nCloses https://github.com/elastic/kibana/issues/265294\n\nIt seems like many tests can run in parallel and target the same default\nindex, at the same time ES can take some time to refresh after setting\nthe new default. To fix this there are 2 main changes, the first one is\nto poll the GET endpoint until the index matches the new one that was\nset. The second change is to use a different space for each of the\nsuites so that way they are not affected by other tests.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"1b5e94e0a6ebd4182df0c830cf7320575f2b3e4e"}},"sourceBranch":"main","suggestedTargetBranches":["9.4"],"targetPullRequestStates":[{"branch":"main","label":"v9.5.0","branchLabelMappingKey":"^v9.5.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/268370","number":268370,"mergeCommit":{"message":"[Data views/Index Patterns][Scout] Fix set default data view tests (#268370)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/265664\nCloses https://github.com/elastic/kibana/issues/265545\nCloses https://github.com/elastic/kibana/issues/265424\nCloses https://github.com/elastic/kibana/issues/266542\nCloses https://github.com/elastic/kibana/issues/265649\nCloses https://github.com/elastic/kibana/issues/265294\n\nIt seems like many tests can run in parallel and target the same default\nindex, at the same time ES can take some time to refresh after setting\nthe new default. To fix this there are 2 main changes, the first one is\nto poll the GET endpoint until the index matches the new one that was\nset. The second change is to use a different space for each of the\nsuites so that way they are not affected by other tests.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"1b5e94e0a6ebd4182df0c830cf7320575f2b3e4e"}},{"branch":"9.4","label":"v9.4.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: Alejandro García Parrondo <31973472+AlexGPlay@users.noreply.github.com>
This was referenced May 12, 2026
patrykkopycinski
pushed a commit
to patrykkopycinski/kibana
that referenced
this pull request
May 13, 2026
…lastic#268370) ## Summary Closes elastic#265664 Closes elastic#265545 Closes elastic#265424 Closes elastic#266542 Closes elastic#265649 Closes elastic#265294 It seems like many tests can run in parallel and target the same default index, at the same time ES can take some time to refresh after setting the new default. To fix this there are 2 main changes, the first one is to poll the GET endpoint until the index matches the new one that was set. The second change is to use a different space for each of the suites so that way they are not affected by other tests. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [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 - [x] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels.
jcger
pushed a commit
that referenced
this pull request
May 26, 2026
…268370) ## Summary Closes #265664 Closes #265545 Closes #265424 Closes #266542 Closes #265649 Closes #265294 It seems like many tests can run in parallel and target the same default index, at the same time ES can take some time to refresh after setting the new default. To fix this there are 2 main changes, the first one is to poll the GET endpoint until the index matches the new one that was set. The second change is to use a different space for each of the suites so that way they are not affected by other tests. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [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 - [x] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes #265664
Closes #265545
Closes #265424
Closes #266542
Closes #265649
Closes #265294
It seems like many tests can run in parallel and target the same default index, at the same time ES can take some time to refresh after setting the new default. To fix this there are 2 main changes, the first one is to poll the GET endpoint until the index matches the new one that was set. The second change is to use a different space for each of the suites so that way they are not affected by other tests.
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:*label is applied per the guidelinesbackport:*labels.