[8.18] tests: ls2ls delay checking until events have been processed (backport #17167)#17250
Merged
[8.18] tests: ls2ls delay checking until events have been processed (backport #17167)#17250
Conversation
* tests: ls2ls delay checking until events have been processed * Make sure upstream sends expected number of events before checking the expectation with downstream. Remove unnecessary or duplicated logics from the spec. * Add exception handling in `wait_for_rest_api` to make wait for LS REST API retriable. --------- Co-authored-by: Mashhur <mashhur.sattorov@elastic.co> Co-authored-by: Mashhur <99575341+mashhurs@users.noreply.github.com> (cherry picked from commit 73ffa24)
|
💚 Build Succeeded
cc @yaauie |
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.
Release notes
[rn:skip]
What does this PR do?
Resolves flaky logstash-to-logstash integration test that was attempting to validate the processed events after ensuring that the right quantity had been received by adding a guard to ensure that the quantity of events had been processed
Why is it important/What is the impact to the user?
no user impact, speeds up CI by not needing to retry whole integration test jobs
Checklist
[ ] I have commented my code, particularly in hard-to-understand areas[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files (and/or docker env variables)This is an automatic backport of pull request #17167 done by [Mergify](https://mergify.com).