Give more time to multiline parser to aggregate logs into events during testing#30335
Merged
kvch merged 1 commit intoelastic:mainfrom Feb 10, 2022
Merged
Give more time to multiline parser to aggregate logs into events during testing#30335kvch merged 1 commit intoelastic:mainfrom
kvch merged 1 commit intoelastic:mainfrom
Conversation
Contributor
|
This pull request does not have a backport label. Could you fix it @kvch? 🙏
NOTE: |
Contributor
Contributor
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
Contributor
Author
|
jenkins run tests |
rdner
approved these changes
Feb 10, 2022
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
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.
What does this PR do?
This PR reenables previous flaky tests. The problem was that we did not leave enough time for the multiline parser to aggregate log lines into a single message. So we ended up with incomplete events, saving unexpected offsets to the registry.
The fix is to increase the timeout of the multiline parser. The default value is 5 seconds, but I set it to 3, so we still save some time during testing.
Why is it important?
Run existing tests to make sure we do not introduce regressions.
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- [ ] I have added tests that prove my fix is effective or that my feature works- [ ] I have added an entry inCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Related issues
Closes #27893
Closes #27894
Closes #28088
Closes #27085