-
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] coreinternal/consumerretry/logs_test.go failed on windows #28694
Comments
Pinging code owners for internal/core: @open-telemetry/collector-approvers. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
I tried multiple runs on my box and got no repro. However, by code inspection I can see, that due to some concurrency on the test code, how both errors could happen. In theory the fix can happen on any system not only Windows. The fix should be entirely on the test code. Giving that this one seems hard to repro I'm giving it a low priority on my work queue, if some volunteer wants to fix them, please do so. |
Removing |
Hit the first one on my fork - documenting here to give a sense of frequency so we can prioritize them accordingly
|
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. |
Component(s)
internal/core
What happened?
internal/coreinternal/consumerretry/logs_test.go
is broken on Windows test matrix on mainline https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/workflows/build-and-test-windows.yml?query=branch%3AmainCollector version
mainline
Environment information
Environment
OS: Windows
OpenTelemetry Collector configuration
No response
Log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: