-
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] Testintegration getting timed out #26097
Comments
Pinging code owners for receiver/flinkmetrics: @JonathanWamsley @djaglowski. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue came up in workflows for #24774. In one case, noted what I thought were a few key points for summary...
Also want to throw out there that on a follow-up run trying to work through this I saw the same pattern with Hoping to come up with some more concrete causes and changes from there. |
Thanks @nslaughter.
If you are looking into this, it's likely a good idea to look for a solution that can be built into the package, so that this type of failure can be prevented broadly. |
Run into this couple times in https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/6003150441/job/16281731431?pr=26125 I think we should skip the test for now |
Submitted #26194 |
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. |
I'll note that I've had issues with |
I've proposed removing this test in #30218 |
Closed by #30218 |
Description
Flaky test:
https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/5966235030/job/16185463868?pr=26086#step:5:609
https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/5966235030/job/16186427803
The text was updated successfully, but these errors were encountered: