Skip to content

[8.19] fix flaky integration test related to bulk schedule gap fills (#225079) #225946

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

Merged
merged 2 commits into from
Jul 1, 2025

Conversation

kibanamachine
Copy link
Contributor

Backport

This will backport the following commits from main to 8.19:

Questions ?

Please refer to the Backport tool documentation

…c#225079)

## Summary
Fixes elastic#224615
The failure happens because we expect all the unfilled intervals for the
generated gaps to be in progress. However this does not happen all the
time mainly because we are creating the dates of the bulk schedule gap
fills way before the tests run.
The fix is done by grouping the tests that require gaps in their own
describe. Then in their before each statement, we loop through the
created gaps to get the start and end date of the bulk schedule gap
fills request.
Flaky test runner before the changes:
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8418
❌
Flaky test runner with the changes:
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8438
✅

(cherry picked from commit c42533c)
@kibanamachine kibanamachine force-pushed the backport/8.19/pr-225079 branch from 3f88eef to cd37ce9 Compare July 1, 2025 07:46
@elasticmachine
Copy link
Contributor

elasticmachine commented Jul 1, 2025

💔 Build Failed

Failed CI Steps

History

cc @denar50

@kibanamachine kibanamachine merged commit bbc677c into elastic:8.19 Jul 1, 2025
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants