-
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/windowseventlog] Flaky test TestReadWindowsEventLogger #34687
Comments
Pinging code owners: See Adding Labels via Comments if you do not have permissions to add labels yourself. |
/label os:windows |
I thought this was due to other changes in the PR but it appears to be pre-existing. |
Yes, @djaglowski - I was glancing at the test code and there are many non-reliable things happening in the tests. I will start working on improving these tests. |
) **Description:** There are 3 main issues being addressed on this PR: * There is a race between start and generating the events in the tests: the start require goroutines so a delay before generating the events will be advisable (not perfect but good enough per my tests) * The tests assume that only the tests are generating events in that time window, that is impossible to guarantee on a windows box, so instead of checking for exactly one event they need to get new events and check the event provider instead * The exclusion test checks if zero events were delivered by the receiver, it should check if one not filtered out was received, and this one should be generated after the event from the provider that should be excluded. **Link to tracking Issue:** Fixes open-telemetry#34687 **Testing:** Multiple local runs, we should do a few runs on CI given the runner characteristics. **Documentation:** N/A
This is still happening https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/11371732717/job/31634469890
|
A different test, but, for now keeping track of this failure here, they may have the same root cause - will open separate issue/PR is appropriate.
|
Another error on the same receiver, a different one:
|
The data race at #34687 (comment) seems due to the use of |
Fixes a data race detected [here](#34687 (comment)). This doesn't solve the flakiness detected on this receiver tests, only avoids the data race.
Component(s)
receiver/windowseventlog
Describe the issue you're reporting
Flaky test: https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/10391822945/job/28775648414?pr=34656#step:6:571
The text was updated successfully, but these errors were encountered: