-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
check tests/integration/instrumentation flakyness #5545
Comments
The root cause is due to improper shutdown of the opentelmetry grpc client. Each test is creating all docker dependencies and then destroying at the end of the test. Since the client running in a different thread doesn't shutdown properly and leads to a segmentation fault. The gprc client has a very large back off 64s which is long compared to the length of the test execution. |
Waiting for review of open-telemetry/opentelemetry-python#3138. |
The instrumentation worker runs in a daemon thread/s in:
Is there a way to make sure that this thread terminates before closing the Flow context manager. The logs clearly show that the exporter is still working in the background due to the max 64s exponential back off retry logic. |
Every Runtime is ensured to call the |
Ww should be able to call this |
The runtime already does call the shutdown but the code doesn't break the exponential back off and retry loop. I have asked a question in my pr regarding the cancellation of the retry after shutdown is set. |
Seems related to https://bugs.python.org/issue39853 and the same problem as astropy/astropy#10008 |
Describe the bug
This test tests/integration/instrumentation looks very flaky and do not let us work with 3.8
The text was updated successfully, but these errors were encountered: