-
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
[receiver/sqlquery] Broken Test TestPostgresIntegrationLogsTrackingWithStorage #31782
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Pinging code owners for receiver/sqlquery: @dmitryax @crobert-1. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Thanks for filing, I'll take a look when I get a chance 👍 Pasting the test failure output:
|
@crobert-1 I need to keep investigating #31778 as it is possible the issue isn't the test but something in core. |
Just a note, nothing in that PR is relevant to this test failure. A couple specific tests were changed (unrelated to this failure), and goleak was added. Failures from
|
Ya IDK why it switched the green check to a red x for those tests, so that is suspicious, but I dont think anymore that it is causing the failure in my PR. If you have any ideas why #31778 is failing that test with the latest from core please let me know, im stumped at the moment. |
**Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> This PR includes two changes that are dependent on each other. 1. Fix test failing in #31778. Explanation given [here.](#31778 (comment)) All changes in `integration_test.go` are related to this. 2. When the test was fixed, `goleak` started failing. The logs receiver opens a DB connection when it's started, but shutdown does not close the DB. This DB needs to be closed during shutdown to avoid a leaked goroutine. All changes outside of `integration_test.go` are for this. 3. Since the memory leak changes were modifying errors, I moved from using `multierr.append` to `errors.Join` as well. **Link to tracking Issue:** <Issue number if applicable> Resolves #31782 Related to #31778 **Testing:** <Describe what testing was performed and which tests were added.> Tests are passing
Component(s)
receiver/sqlquery
What happened?
Since #31667 was merged the
TestPostgresIntegrationLogsTrackingWithStorage
integration test has started failing silently for some reason.You can see the failures inside the
Run Integration Test
step in jobs like:any another other job since.
For some reason my
update-otel
PR is actually showing the failure: https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/8300689476/job/22720973013Collector version
Latest
Environment information
No response
OpenTelemetry Collector configuration
No response
Log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: