-
Notifications
You must be signed in to change notification settings - Fork 5k
[oteltest][fbreceiver] Fix flaky test #45127
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
Conversation
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
ecaecdb
to
35dcc0c
Compare
35dcc0c
to
b2cb0c1
Compare
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
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.
Can you check the tests that use this suite as well, to make sure they do not use t inside AssertFunc? Thank you!
yeah, there are some occurrences. I'll update the PR. |
* skip TestReceiverDegraded * typo * commit * replace require.EventuallyWithT (cherry picked from commit dd5cbac) # Conflicts: # libbeat/otelbeat/oteltest/oteltest.go # x-pack/filebeat/fbreceiver/receiver_test.go
* skip TestReceiverDegraded * typo * commit * replace require.EventuallyWithT (cherry picked from commit dd5cbac)
In our otelbeat's test cases, we use
require.EventuallyWithT
to test certain conditions which are satisfied after some time. For eg. status reporter.While asserting conditions, we should pass
*assert.CollectT
variable and not the parenttesting.T
. Passing the parent variable will lead to instant failure because of the underlying logic ofEventuallyWithT
.Closes #45057