Log an error instead of an info event when the local inference thread of PolicyClient
Log an error instead of an info event when the local inference thread of PolicyClient
Why are these changes needed?
Better debug-ability when a crash occurs in the PolicyClient when using the _LocalInferenceThread. If one was running rllib with loglevel 'warning/error/critical', one would miss an exception/crash of the reason, unless the loglevel was 'info'.
Related issue number
Closes #30174
Checks
- [X] I've signed off every commit(by using the -s flag, i.e.,
git commit -s) in this PR. - [X] I've run
scripts/format.shto lint the changes in this PR. - [X] I've included any doc changes needed for https://docs.ray.io/en/master/.
- [X] I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
- Testing Strategy
- [X] Unit tests
- [ ] Release tests
- [ ] This PR is not tested :(
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.
- If you'd like to keep this open, just leave any comment, and the stale label will be removed.
Removing stale label, @sven1977 could you have a look?
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.
- If you'd like to keep this open, just leave any comment, and the stale label will be removed.
destaling..
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.
- If you'd like to keep this open, just leave any comment, and the stale label will be removed.
Hi @avnishn ,
Could you also give this review a look and merge if ok?
Trying another maintainer @krfricke, could you do a review?
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.
- If you'd like to keep this open, just leave any comment, and the stale label will be removed.
Removing stale label..