-
Notifications
You must be signed in to change notification settings - Fork 141
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
Add jds-do-not-fail-on-jdc-shutdown integration test #1360
Add jds-do-not-fail-on-jdc-shutdown integration test #1360
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1360 +/- ##
==========================================
- Coverage 18.79% 17.95% -0.85%
==========================================
Files 167 167
Lines 11348 11936 +588
==========================================
+ Hits 2133 2143 +10
- Misses 9215 9793 +578
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
68191ad
to
e0825a8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks super with the tests!
a2203ff
to
5b42f52
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Added few nits. Could you also please apply the docs changes to JDC::shutdown?
086f3a4
to
6f05a39
Compare
@Shourya742 Please fixup 6f05a39 to its correct place |
b933a2b
to
d147540
Compare
d147540
to
353c1d6
Compare
…iding shutdown handler
…hutdown handler add unit test for jdc shutdown api
This is crucial because when the `start` method is executed in a runtime that is not the main one, the lifecycle of futures spawned within the `start` method continues, even after the `jdc` process terminates.The earlier approach of simply exiting the loop worked because the `start` method was executed on the main blocking thread, where the Tokio runtime was defined. However, in the case of integration tests, the runtime runs on a different blocking thread, necessitating proper handling of the root future termination.
…est from test module
353c1d6
to
1fe2395
Compare
Closes: #1348 #1320 #1349