-
Notifications
You must be signed in to change notification settings - Fork 75
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
fix: shutdown cluster test timeout #918
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #918 +/- ##
==========================================
- Coverage 75.55% 75.20% -0.36%
==========================================
Files 180 190 +10
Lines 26938 28480 +1542
Branches 26938 28480 +1542
==========================================
+ Hits 20353 21418 +1065
- Misses 5366 5769 +403
- Partials 1219 1293 +74 ☔ View full report in Codecov by Sentry. |
This PR is stale because it has been open for 30 days with no activity. Remove stale label or comment or this will be closed in 14 days |
1607307
to
527a3c9
Compare
@lxl66566 Convert your pr to draft since CI failed |
This PR is stale because it has been open for 30 days with no activity. Remove stale label or comment or this will be closed in 14 days |
Signed-off-by: lxl66566 <[email protected]> chore: add more docs Signed-off-by: lxl66566 <[email protected]>
Please briefly answer these questions:
what problem are you trying to solve? (or if there's no problem, what's the motivation for this change?)
what changes does this pull request make?
shutdown_rpc_should_shutdown_the_cluster()
: make put thread return faster when retry count up to max times.are there any non-obvious implications of these changes? (does it break compatibility with previous versions, etc)