Skip to content

[CI] Disable test rerun optimization for flaky tests#242852

Merged
delanni merged 2 commits intoelastic:mainfrom
delanni:disable-test-rerun-optimization-for-flaky-tests
Nov 13, 2025
Merged

[CI] Disable test rerun optimization for flaky tests#242852
delanni merged 2 commits intoelastic:mainfrom
delanni:disable-test-rerun-optimization-for-flaky-tests

Conversation

@delanni
Copy link
Copy Markdown
Member

@delanni delanni commented Nov 13, 2025

Summary

After #237705 - it seems flaky test runs have been optimizing and skipping already successfully tested runs - this is not a desired behavior, so let's skip this optimization for flaky test runs.

…est config active - that feature in flaky-tests is counter-productive
@delanni delanni requested a review from a team as a code owner November 13, 2025 10:17
@delanni delanni added Team:Operations Kibana-Operations Team release_note:skip Skip the PR/issue when compiling release notes backport:all-open Backport to all branches that could still receive a release labels Nov 13, 2025
@elasticmachine
Copy link
Copy Markdown
Contributor

Pinging @elastic/kibana-operations (Team:Operations)

@elasticmachine
Copy link
Copy Markdown
Contributor

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

  • [job] [logs] Scout: [ platform / streams_app ] plugin / serverless-oblt - Stream data processing - error handling and recovery - should recover from API errors during a processor updates
  • [job] [logs] Scout: [ platform / streams_app ] plugin / should recover from API errors during a processor updates

Metrics [docs]

✅ unchanged

@delanni delanni merged commit 4a4e580 into elastic:main Nov 13, 2025
21 checks passed
@delanni delanni deleted the disable-test-rerun-optimization-for-flaky-tests branch November 13, 2025 13:06
@kibanamachine
Copy link
Copy Markdown
Contributor

Starting backport for target branches: 8.19, 9.1, 9.2

https://github.com/elastic/kibana/actions/runs/19332558460

@kibanamachine
Copy link
Copy Markdown
Contributor

💔 All backports failed

Status Branch Result
8.19 Backport failed because of merge conflicts
9.1 Backport failed because of merge conflicts
9.2 Backport failed because of merge conflicts

Manual backport

To create the backport manually run:

node scripts/backport --pr 242852

Questions ?

Please refer to the Backport tool documentation

@kibanamachine kibanamachine added the backport missing Added to PRs automatically when the are determined to be missing a backport. label Nov 14, 2025
@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 242852 locally
cc: @delanni

2 similar comments
@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 242852 locally
cc: @delanni

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 242852 locally
cc: @delanni

delanni added a commit to kibanamachine/kibana that referenced this pull request Nov 19, 2025
## Summary
After elastic#237705 - it seems flaky
test runs have been optimizing and skipping already successfully tested
runs - this is not a desired behavior, so let's skip this optimization
for flaky test runs.
delanni added a commit to kibanamachine/kibana that referenced this pull request Nov 19, 2025
## Summary
After elastic#237705 - it seems flaky
test runs have been optimizing and skipping already successfully tested
runs - this is not a desired behavior, so let's skip this optimization
for flaky test runs.
delanni added a commit to kibanamachine/kibana that referenced this pull request Nov 19, 2025
## Summary
After elastic#237705 - it seems flaky
test runs have been optimizing and skipping already successfully tested
runs - this is not a desired behavior, so let's skip this optimization
for flaky test runs.
@delanni delanni added backport:skip This PR does not require backporting and removed backport:all-open Backport to all branches that could still receive a release labels Nov 19, 2025
@kibanamachine kibanamachine removed the backport missing Added to PRs automatically when the are determined to be missing a backport. label Nov 19, 2025
eokoneyo pushed a commit to eokoneyo/kibana that referenced this pull request Dec 2, 2025
## Summary
After elastic#237705 - it seems flaky
test runs have been optimizing and skipping already successfully tested
runs - this is not a desired behavior, so let's skip this optimization
for flaky test runs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:skip This PR does not require backporting release_note:skip Skip the PR/issue when compiling release notes Team:Operations Kibana-Operations Team v9.3.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants