-
Notifications
You must be signed in to change notification settings - Fork 1.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
TestQueuedRetryPersistentEnabled_shutdown_dataIsRequeued is flaky #8124
Labels
bug
Something isn't working
Comments
Still happening, slight change of line numbers:
|
This was referenced Nov 23, 2023
bogdandrutu
pushed a commit
that referenced
this issue
Nov 23, 2023
…8986) Fix flaky TestQueuedRetryPersistentEnabled_shutdown_dataIsRequeued by moving it to persistent queue. - It makes the test easy to validate given that the size of the persistent queue is always available even if it's closed. - It brings behavior closer to the name of the test - It removes the flakiness associated with data race specific to re-enqueuing to the bounded memory queue by shutdown which should be resolved separately once the re-enqueue option is available for the memory queue Fixes #8124
pantuza
pushed a commit
to pantuza/opentelemetry-collector
that referenced
this issue
Dec 8, 2023
…pen-telemetry#8986) Fix flaky TestQueuedRetryPersistentEnabled_shutdown_dataIsRequeued by moving it to persistent queue. - It makes the test easy to validate given that the size of the persistent queue is always available even if it's closed. - It brings behavior closer to the name of the test - It removes the flakiness associated with data race specific to re-enqueuing to the bounded memory queue by shutdown which should be resolved separately once the re-enqueue option is available for the memory queue Fixes open-telemetry#8124
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See https://github.com/open-telemetry/opentelemetry-collector/actions/runs/5641800307/job/15280483750
The text was updated successfully, but these errors were encountered: