-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[tests][filebeat] fix flaky unit test cases #40389
Conversation
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
/test |
@VihasMakwana I added the
If CI is still green, suggest we run the tests using the trigger phrase a couple of more times -- since it's a flaky test -- to ensure we are good. |
/test |
/test |
/test |
@dliappis looks like it's working. I've ran CI for the fourth time. Let's see how it goes. |
Thank you so much @VihasMakwana for testing this thoroughly, much appreciated! FYI @oakrizan |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Based on #40389 (comment)
LGTM from an ingest-eng-prod PoV. Thank you!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The fix makes sense to me, I see it was well-tested too.
* fix: fix flaky unit test cases * fix: fix test_reload_same_config (cherry picked from commit 4fbf1b1)
* fix: fix flaky unit test cases * fix: fix test_reload_same_config (cherry picked from commit 4fbf1b1)
* fix: fix flaky unit test cases * fix: fix test_reload_same_config (cherry picked from commit 4fbf1b1) Co-authored-by: VihasMakwana <[email protected]>
* fix: fix flaky unit test cases * fix: fix test_reload_same_config (cherry picked from commit 4fbf1b1) Co-authored-by: VihasMakwana <[email protected]>
Proposed commit message
/logs/*
pattern.ndjson
file (which we shouldn't, as it's the output file) and this would cause test case failure.logs/*.log
as the patternRunner: 'xyz' has stopped
to determine the stoppage instead ofStopping runner
. The later would fail if there are transient errors.Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Disruptive User Impact
Author's Checklist
How to test this PR locally
Related issues
tests/system/*.py
) #40237Use cases
Screenshots
Logs