-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[flaky test][receiver/collectdreceiver] Lifecycle test failing due to bind: address already in use #30805
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
It looks like the lifecycle test starts a receiver, shuts it down, then starts another with the exact same config, binding to the same endpoint. I believe there may be a goroutine leak going on here that's causing this, judging by the context of the test failure, the low frequency of the test failure, and the fact that |
Appreciated, it looks like the tests are catching an interesting issue. Thanks for the report. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
receiver/collectd
Describe the issue you're reporting
Failure link: https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/7673900683/job/20917582102?pr=30803
The text was updated successfully, but these errors were encountered: