Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Failing test: Jest Integration Tests.src/core/server/integration_tests/saved_objects/migrations/group3/actions - migration actions waitForPickupUpdatedMappingsTask resolves left wait_for_task_completion_timeout when the task does not complete within the timeout #166199

Closed
kibanamachine opened this issue Sep 11, 2023 · 18 comments · Fixed by #168848 or #204561
Closed

Failing test: Jest Integration Tests.src/core/server/integration_tests/saved_objects/migrations/group3/actions - migration actions waitForPickupUpdatedMappingsTask resolves left wait_for_task_completion_timeout when the task does not complete within the timeout #166199

kibanamachine opened this issue Sep 11, 2023 · 18 comments · Fixed by #168848 or #204561
Assignees
@gsoldevila
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Sep 11, 2023 •
edited
Loading

A test failed on a tracked branch

Error: expect(received).resolves.toMatchObject()

Received promise rejected instead of resolved
Rejected to value: [Error: pickupUpdatedMappings task failed with the following error:
{"type":"index_not_found_exception","reason":"no such index [.kibana_1]","resource.type":"index_or_alias","resource.id":".kibana_1","index_uuid":"_na_","index":".kibana_1"}]
    at expect (/var/lib/buildkite-agent/builds/kb-n2-4-spot-967787861bb42ff1/elastic/kibana-on-merge/kibana/node_modules/expect/build/index.js:113:15)
    at Object.expect (/var/lib/buildkite-agent/builds/kb-n2-4-spot-967787861bb42ff1/elastic/kibana-on-merge/kibana/src/core/server/integration_tests/saved_objects/migrations/group3/actions/actions_test_suite.ts:1479:13)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)

First failure: CI Build - main
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Sep 11, 2023
@botelastic botelastic bot added the needs-team Issues missing a team label label Sep 11, 2023
@kibanamachine kibanamachine added the Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc label Sep 11, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-core (Team:Core)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Sep 11, 2023
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

jbudz added a commit that referenced this issue Sep 11, 2023
@jbudz
skip failing test suite (#166199)
2f1da3c
@jbudz
Copy link
Member

jbudz commented Sep 11, 2023

Skipped

main: 2f1da3c

@rudolf rudolf self-assigned this Oct 12, 2023
@rudolf rudolf mentioned this issue Oct 13, 2023
Merged
9 tasks
rudolf added a commit that referenced this issue Oct 23, 2023
@rudolf @kibanamachine
Fix flaky migrations actions test by using an index with more docs (#…
3610091 
…168848)

## Summary

Second attempt at:
fixes #166190 
fixes #166199


More data, more timeout 👯 I have not been able to cause this to fail
locally, but we don't have a flaky test running for jest integrations
tests to confirm. So the only way to fully test is to merge.

### Checklist

Delete any items that are not applicable to this PR.

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [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
- [ ] Any UI touched in this PR is usable by keyboard only (learn more
about [keyboard accessibility](https://webaim.org/techniques/keyboard/))
- [ ] Any UI touched in this PR does not create any new axe failures
(run axe in browser:
[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),
[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This renders correctly on smaller devices using a responsive
layout. (You can test this [in your
browser](https://www.browserstack.com/guide/responsive-testing-on-local-server))
- [ ] This was checked for [cross-browser
compatibility](https://www.elastic.co/support/matrix#matrix_browsers)


### Risk Matrix

Delete this section if it is not applicable to this PR.

Before closing this PR, invite QA, stakeholders, and other developers to
identify risks that should be tested prior to the change/feature
release.

When forming the risk matrix, consider some of the following examples
and how they may potentially impact the change:

| Risk | Probability | Severity | Mitigation/Notes |

|---------------------------|-------------|----------|-------------------------|
| Multiple Spaces—unexpected behavior in non-default Kibana Space.
| Low | High | Integration tests will verify that all features are still
supported in non-default Kibana Space and when user switches between
spaces. |
| Multiple nodes—Elasticsearch polling might have race conditions
when multiple Kibana nodes are polling for the same tasks. | High | Low
| Tasks are idempotent, so executing them multiple times will not result
in logical error, but will degrade performance. To test for this case we
add plenty of unit tests around this logic and document manual testing
procedure. |
| Code should gracefully handle cases when feature X or plugin Y are
disabled. | Medium | High | Unit tests will verify that any feature flag
or plugin combination still results in our service operational. |
| [See more potential risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) |


### 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)

---------

Co-authored-by: Kibana Machine <[email protected]>
kibanamachine pushed a commit to kibanamachine/kibana that referenced this issue Oct 23, 2023
@rudolf
Fix flaky migrations actions test by using an index with more docs (e…
9d2ba17 
…lastic#168848)

## Summary

Second attempt at:
fixes elastic#166190
fixes elastic#166199

More data, more timeout 👯 I have not been able to cause this to fail
locally, but we don't have a flaky test running for jest integrations
tests to confirm. So the only way to fully test is to merge.

### Checklist

Delete any items that are not applicable to this PR.

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [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
- [ ] Any UI touched in this PR is usable by keyboard only (learn more
about [keyboard accessibility](https://webaim.org/techniques/keyboard/))
- [ ] Any UI touched in this PR does not create any new axe failures
(run axe in browser:
[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),
[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This renders correctly on smaller devices using a responsive
layout. (You can test this [in your
browser](https://www.browserstack.com/guide/responsive-testing-on-local-server))
- [ ] This was checked for [cross-browser
compatibility](https://www.elastic.co/support/matrix#matrix_browsers)

### Risk Matrix

Delete this section if it is not applicable to this PR.

Before closing this PR, invite QA, stakeholders, and other developers to
identify risks that should be tested prior to the change/feature
release.

When forming the risk matrix, consider some of the following examples
and how they may potentially impact the change:

| Risk | Probability | Severity | Mitigation/Notes |

|---------------------------|-------------|----------|-------------------------|
| Multiple Spaces&mdash;unexpected behavior in non-default Kibana Space.
| Low | High | Integration tests will verify that all features are still
supported in non-default Kibana Space and when user switches between
spaces. |
| Multiple nodes&mdash;Elasticsearch polling might have race conditions
when multiple Kibana nodes are polling for the same tasks. | High | Low
| Tasks are idempotent, so executing them multiple times will not result
in logical error, but will degrade performance. To test for this case we
add plenty of unit tests around this logic and document manual testing
procedure. |
| Code should gracefully handle cases when feature X or plugin Y are
disabled. | Medium | High | Unit tests will verify that any feature flag
or plugin combination still results in our service operational. |
| [See more potential risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) |

### 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)

---------

Co-authored-by: Kibana Machine <[email protected]>
(cherry picked from commit 3610091)
kibanamachine referenced this issue Oct 23, 2023
@kibanamachine @rudolf
[8.11] Fix flaky migrations actions test by using an index with more …
5cd6b31 
…docs (#168848) (#169536)

# Backport

This will backport the following commits from `main` to `8.11`:
- [Fix flaky migrations actions test by using an index with more docs
(#168848)](#168848)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Rudolf
Meijering","email":"[email protected]"},"sourceCommit":{"committedDate":"2023-10-23T14:12:13Z","message":"Fix
flaky migrations actions test by using an index with more docs
(#168848)\n\n## Summary\r\n\r\nSecond attempt at:\r\nfixes
#166190 \r\nfixes
https://github.com/elastic/kibana/issues/166199\r\n\r\n\r\nMore data,
more timeout 👯 I have not been able to cause this to fail\r\nlocally,
but we don't have a flaky test running for jest integrations\r\ntests to
confirm. So the only way to fully test is to merge.\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n-
[ ] Any UI touched in this PR does not create any new axe
failures\r\n(run axe in
browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n-
[ ] If a plugin configuration key changed, check if it needs to
be\r\nallowlisted in the cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n###
Risk Matrix\r\n\r\nDelete this section if it is not applicable to this
PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other
developers to\r\nidentify risks that should be tested prior to the
change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider
some of the following examples\r\nand how they may potentially impact
the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes
|\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n|
Multiple Spaces&mdash;unexpected behavior in non-default Kibana
Space.\r\n| Low | High | Integration tests will verify that all features
are still\r\nsupported in non-default Kibana Space and when user
switches between\r\nspaces. |\r\n| Multiple nodes&mdash;Elasticsearch
polling might have race conditions\r\nwhen multiple Kibana nodes are
polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so
executing them multiple times will not result\r\nin logical error, but
will degrade performance. To test for this case we\r\nadd plenty of unit
tests around this logic and document manual testing\r\nprocedure. |\r\n|
Code should gracefully handle cases when feature X or plugin Y
are\r\ndisabled. | Medium | High | Unit tests will verify that any
feature flag\r\nor plugin combination still results in our service
operational. |\r\n| [See more potential
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
|\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for
breaking API changes and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by:
Kibana Machine
<[email protected]>","sha":"36100918ed7180890a60cb9896c66fcc8ae0575e","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport:prev-minor","v8.12.0"],"number":168848,"url":"https://github.com/elastic/kibana/pull/168848","mergeCommit":{"message":"Fix
flaky migrations actions test by using an index with more docs
(#168848)\n\n## Summary\r\n\r\nSecond attempt at:\r\nfixes
#166190 \r\nfixes
https://github.com/elastic/kibana/issues/166199\r\n\r\n\r\nMore data,
more timeout 👯 I have not been able to cause this to fail\r\nlocally,
but we don't have a flaky test running for jest integrations\r\ntests to
confirm. So the only way to fully test is to merge.\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n-
[ ] Any UI touched in this PR does not create any new axe
failures\r\n(run axe in
browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n-
[ ] If a plugin configuration key changed, check if it needs to
be\r\nallowlisted in the cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n###
Risk Matrix\r\n\r\nDelete this section if it is not applicable to this
PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other
developers to\r\nidentify risks that should be tested prior to the
change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider
some of the following examples\r\nand how they may potentially impact
the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes
|\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n|
Multiple Spaces&mdash;unexpected behavior in non-default Kibana
Space.\r\n| Low | High | Integration tests will verify that all features
are still\r\nsupported in non-default Kibana Space and when user
switches between\r\nspaces. |\r\n| Multiple nodes&mdash;Elasticsearch
polling might have race conditions\r\nwhen multiple Kibana nodes are
polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so
executing them multiple times will not result\r\nin logical error, but
will degrade performance. To test for this case we\r\nadd plenty of unit
tests around this logic and document manual testing\r\nprocedure. |\r\n|
Code should gracefully handle cases when feature X or plugin Y
are\r\ndisabled. | Medium | High | Unit tests will verify that any
feature flag\r\nor plugin combination still results in our service
operational. |\r\n| [See more potential
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
|\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for
breaking API changes and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by:
Kibana Machine
<[email protected]>","sha":"36100918ed7180890a60cb9896c66fcc8ae0575e"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/168848","number":168848,"mergeCommit":{"message":"Fix
flaky migrations actions test by using an index with more docs
(#168848)\n\n## Summary\r\n\r\nSecond attempt at:\r\nfixes
#166190 \r\nfixes
https://github.com/elastic/kibana/issues/166199\r\n\r\n\r\nMore data,
more timeout 👯 I have not been able to cause this to fail\r\nlocally,
but we don't have a flaky test running for jest integrations\r\ntests to
confirm. So the only way to fully test is to merge.\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n-
[ ] Any UI touched in this PR does not create any new axe
failures\r\n(run axe in
browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n-
[ ] If a plugin configuration key changed, check if it needs to
be\r\nallowlisted in the cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n###
Risk Matrix\r\n\r\nDelete this section if it is not applicable to this
PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other
developers to\r\nidentify risks that should be tested prior to the
change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider
some of the following examples\r\nand how they may potentially impact
the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes
|\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n|
Multiple Spaces&mdash;unexpected behavior in non-default Kibana
Space.\r\n| Low | High | Integration tests will verify that all features
are still\r\nsupported in non-default Kibana Space and when user
switches between\r\nspaces. |\r\n| Multiple nodes&mdash;Elasticsearch
polling might have race conditions\r\nwhen multiple Kibana nodes are
polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so
executing them multiple times will not result\r\nin logical error, but
will degrade performance. To test for this case we\r\nadd plenty of unit
tests around this logic and document manual testing\r\nprocedure. |\r\n|
Code should gracefully handle cases when feature X or plugin Y
are\r\ndisabled. | Medium | High | Unit tests will verify that any
feature flag\r\nor plugin combination still results in our service
operational. |\r\n| [See more potential
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
|\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for
breaking API changes and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by:
Kibana Machine
<[email protected]>","sha":"36100918ed7180890a60cb9896c66fcc8ae0575e"}}]}]
BACKPORT-->

Co-authored-by: Rudolf Meijering <[email protected]>
@kibanamachine kibanamachine reopened this Oct 23, 2023
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 8.11

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 8.11

mistic added a commit that referenced this issue Oct 24, 2023
@mistic
skip flaky suite (#166199)
255e32a
mistic added a commit that referenced this issue Oct 24, 2023
@mistic
skip flaky suite (#166199)
9f0d7bb
@afharo
Copy link
Member

afharo commented Sep 25, 2024 •
edited
Loading

Reopening because it's actually skipped in main 🤷

kibana/src/core/server/integration_tests/saved_objects/migrations/group3/actions/actions_test_suite.ts

Lines 1447 to 1448 in 8d7dad2

// FLAKY: https://github.com/elastic/kibana/issues/166199
describe.skip('waitForPickupUpdatedMappingsTask', () => {

@afharo afharo reopened this Sep 25, 2024
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-elasticsearch-snapshot-verify - main

@gsoldevila gsoldevila assigned gsoldevila and unassigned rudolf Sep 26, 2024
@gsoldevila
Copy link
Contributor

Addressing this one as I've introduced a small regression

@gsoldevila gsoldevila mentioned this issue Sep 26, 2024
Merged
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

gsoldevila added a commit that referenced this issue Sep 27, 2024
@gsoldevila
[Migrations] Upgrade integration tests - follow up work (#194151)
c70757c 
## Summary

*  Fix issue with `docVersion` on link (prevent future failure)
* Add a package to `actions.test.ts` (some of the actions targeted a
pre-existing index).
  * Addresses #166190
  * Addresses #166199
* Fix flakiness in `fail_on_rollback.test.ts`
  * Addresses #193756
@gsoldevila
Copy link
Contributor

Hopefully fixed by #194151

@afharo afharo mentioned this issue Dec 17, 2024
Merged
afharo added a commit that referenced this issue Dec 17, 2024
@afharo
Update data archives for SO integration tests (#204561)
523372f 
## Summary

Bumping the data archives to 8.last (8.18 at the moment) so that ES 9.0
finds it compatible.

Resolves #158318.
Resolves #163254.
Resolves #163255.
Resolves #166190.
Resolves #166199.
Resolves #167676.
kibanamachine pushed a commit to kibanamachine/kibana that referenced this issue Dec 17, 2024
@afharo
Update data archives for SO integration tests (elastic#204561)
cfee875 
## Summary

Bumping the data archives to 8.last (8.18 at the moment) so that ES 9.0
finds it compatible.

Resolves elastic#158318.
Resolves elastic#163254.
Resolves elastic#163255.
Resolves elastic#166190.
Resolves elastic#166199.
Resolves elastic#167676.

(cherry picked from commit 523372f)
kibanamachine added a commit that referenced this issue Dec 17, 2024
@kibanamachine @afharo
[8.x] Update data archives for SO integration tests (#204561) (#204581)
07b2420 
# Backport

This will backport the following commits from `main` to `8.x`:
- [Update data archives for SO integration tests
(#204561)](#204561)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Alejandro Fernández
Haro","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-17T14:18:48Z","message":"Update
data archives for SO integration tests (#204561)\n\n##
Summary\n\nBumping the data archives to 8.last (8.18 at the moment) so
that ES 9.0\nfinds it compatible.\n\nResolves #158318.\nResolves
#163254.\nResolves #163255.\nResolves #166190.\nResolves
#166199.\nResolves
#167676.","sha":"523372fd6e3c04134f70c9fc05ead121b6922181","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","v9.0.0","backport:prev-minor"],"title":"Update
data archives for SO integration
tests","number":204561,"url":"https://github.com/elastic/kibana/pull/204561","mergeCommit":{"message":"Update
data archives for SO integration tests (#204561)\n\n##
Summary\n\nBumping the data archives to 8.last (8.18 at the moment) so
that ES 9.0\nfinds it compatible.\n\nResolves #158318.\nResolves
#163254.\nResolves #163255.\nResolves #166190.\nResolves
#166199.\nResolves
#167676.","sha":"523372fd6e3c04134f70c9fc05ead121b6922181"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/204561","number":204561,"mergeCommit":{"message":"Update
data archives for SO integration tests (#204561)\n\n##
Summary\n\nBumping the data archives to 8.last (8.18 at the moment) so
that ES 9.0\nfinds it compatible.\n\nResolves #158318.\nResolves
#163254.\nResolves #163255.\nResolves #166190.\nResolves
#166199.\nResolves
#167676.","sha":"523372fd6e3c04134f70c9fc05ead121b6922181"}}]}]
BACKPORT-->

Co-authored-by: Alejandro Fernández Haro <[email protected]>
JoseLuisGJ pushed a commit to JoseLuisGJ/kibana that referenced this issue Dec 19, 2024
@afharo @JoseLuisGJ
Update data archives for SO integration tests (elastic#204561)
899e397 
## Summary

Bumping the data archives to 8.last (8.18 at the moment) so that ES 9.0
finds it compatible.

Resolves elastic#158318.
Resolves elastic#163254.
Resolves elastic#163255.
Resolves elastic#166190.
Resolves elastic#166199.
Resolves elastic#167676.
benakansara pushed a commit to benakansara/kibana that referenced this issue Jan 2, 2025
@afharo @benakansara
Update data archives for SO integration tests (elastic#204561)
76a7e3e 
## Summary

Bumping the data archives to 8.last (8.18 at the moment) so that ES 9.0
finds it compatible.

Resolves elastic#158318.
Resolves elastic#163254.
Resolves elastic#163255.
Resolves elastic#166190.
Resolves elastic#166199.
Resolves elastic#167676.
CAWilson94 pushed a commit to CAWilson94/kibana that referenced this issue Jan 13, 2025
@afharo @CAWilson94
Update data archives for SO integration tests (elastic#204561)
1d45b20 
## Summary

Bumping the data archives to 8.last (8.18 at the moment) so that ES 9.0
finds it compatible.

Resolves elastic#158318.
Resolves elastic#163254.
Resolves elastic#163255.
Resolves elastic#166190.
Resolves elastic#166199.
Resolves elastic#167676.
viduni94 pushed a commit to viduni94/kibana that referenced this issue Jan 23, 2025
@afharo @viduni94
Update data archives for SO integration tests (elastic#204561)
71c7ceb 
## Summary

Bumping the data archives to 8.last (8.18 at the moment) so that ES 9.0
finds it compatible.

Resolves elastic#158318.
Resolves elastic#163254.
Resolves elastic#163255.
Resolves elastic#166190.
Resolves elastic#166199.
Resolves elastic#167676.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gsoldevila gsoldevila

Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Milestone
No milestone
8 participants
@rudolf @pgayvallet @jbudz @mistic @afharo @elasticmachine @gsoldevila @kibanamachine