[ResponseOps] Fix for flaky test x-pack/test/alerting_api_integration/spaces_only/tests/actions/migrations·ts #182279
Conversation
This file contains 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
doakalexi
changed the title
doakalexi
added
Team:ResponseOps
|
Pinging @elastic/response-ops (Team:ResponseOps) |
ymao1
approved these changes
May 2, 2024
|
/ci |
💚 Build Succeeded
Metrics [docs]
To update your PR or re-run it, just comment with: |
💔 All backports failed
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
doakalexi
added a commit
to doakalexi/kibana
that referenced
this pull request
May 2, 2024
…/spaces_only/tests/actions/migrations·ts (elastic#182279) Resolves elastic#169159 ## Summary I could not reproduce the failure in this test, but it's using `esArchiver` which is known to be flaky. I followed the instructions in this issue, [Proactively improve robustness of FTR tests that use esArchiver elastic#161882](elastic#161882), to help reduce flakiness in the future. Flaky test runner: [run 1](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5829#_) x 50 [run 2](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5830) x 200 [run 3](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5831) x 200 (cherry picked from commit e062a9f) # Conflicts: # x-pack/test/alerting_api_integration/spaces_only/tests/actions/migrations.ts
doakalexi
added a commit
that referenced
this pull request
May 2, 2024
…gration/spaces_only/tests/actions/migrations·ts (#182279) (#182506) # Backport This will backport the following commits from `main` to `8.14`: - [[ResponseOps] Fix for flaky test x-pack/test/alerting_api_integration/spaces_only/tests/actions/migrations·ts (#182279)](#182279) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Alexi Doak","email":"109488926+doakalexi@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-05-02T18:33:58Z","message":"[ResponseOps] Fix for flaky test x-pack/test/alerting_api_integration/spaces_only/tests/actions/migrations·ts (#182279)\n\nResolves https://github.com/elastic/kibana/issues/169159\r\n\r\n## Summary\r\n\r\nI could not reproduce the failure in this test, but it's using\r\n`esArchiver` which is known to be flaky. I followed the instructions in\r\nthis issue, [Proactively improve robustness of FTR tests that use\r\nesArchiver #161882](#161882), to\r\nhelp reduce flakiness in the future.\r\n\r\nFlaky test runner:\r\n[run\r\n1](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5829#_)\r\nx 50\r\n[run\r\n2](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5830)\r\nx 200\r\n[run\r\n3](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5831)\r\nx 200","sha":"e062a9fbc9696ca872da98de63fb598b65ea6467","branchLabelMapping":{"^v8.15.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","v8.14.0","v8.15.0"],"number":182279,"url":"https://github.com/elastic/kibana/pull/182279","mergeCommit":{"message":"[ResponseOps] Fix for flaky test x-pack/test/alerting_api_integration/spaces_only/tests/actions/migrations·ts (#182279)\n\nResolves https://github.com/elastic/kibana/issues/169159\r\n\r\n## Summary\r\n\r\nI could not reproduce the failure in this test, but it's using\r\n`esArchiver` which is known to be flaky. I followed the instructions in\r\nthis issue, [Proactively improve robustness of FTR tests that use\r\nesArchiver #161882](#161882), to\r\nhelp reduce flakiness in the future.\r\n\r\nFlaky test runner:\r\n[run\r\n1](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5829#_)\r\nx 50\r\n[run\r\n2](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5830)\r\nx 200\r\n[run\r\n3](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5831)\r\nx 200","sha":"e062a9fbc9696ca872da98de63fb598b65ea6467"}},"sourceBranch":"main","suggestedTargetBranches":["8.14"],"targetPullRequestStates":[{"branch":"8.14","label":"v8.14.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.15.0","labelRegex":"^v8.15.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/182279","number":182279,"mergeCommit":{"message":"[ResponseOps] Fix for flaky test x-pack/test/alerting_api_integration/spaces_only/tests/actions/migrations·ts (#182279)\n\nResolves https://github.com/elastic/kibana/issues/169159\r\n\r\n## Summary\r\n\r\nI could not reproduce the failure in this test, but it's using\r\n`esArchiver` which is known to be flaky. I followed the instructions in\r\nthis issue, [Proactively improve robustness of FTR tests that use\r\nesArchiver #161882](#161882), to\r\nhelp reduce flakiness in the future.\r\n\r\nFlaky test runner:\r\n[run\r\n1](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5829#_)\r\nx 50\r\n[run\r\n2](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5830)\r\nx 200\r\n[run\r\n3](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5831)\r\nx 200","sha":"e062a9fbc9696ca872da98de63fb598b65ea6467"}}]}] BACKPORT-->
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Resolves #169159
Summary
I could not reproduce the failure in this test, but it's using
esArchiverwhich is known to be flaky. I followed the instructions in this issue, Proactively improve robustness of FTR tests that use esArchiver #161882, to help reduce flakiness in the future.Flaky test runner:
run 1 x 50
run 2 x 200
run 3 x 200