Closed alesnovak-s1 closed 5 months ago
20 files ±0 20 suites ±0 30m 23s :stopwatch: - 2m 52s 1 486 tests +1 1 466 :heavy_check_mark: +1 20 :zzz: ±0 0 :x: ±0 7 101 runs +5 6 874 :heavy_check_mark: +3 227 :zzz: +2 0 :x: ±0
Results for commit bdaa12e8. ± Comparison against base commit 47390e30.
:recycle: This comment has been updated with latest results.
Attention: Patch coverage is 87.80488%
with 5 lines
in your changes are missing coverage. Please review.
Project coverage is 78.31%. Comparing base (
b514d71
) to head (568b57d
). Report is 5 commits behind head on master.:exclamation: Current head 568b57d differs from pull request most recent head bdaa12e. Consider uploading reports for the commit bdaa12e to get more accurate results
After several attempts to make syslog monitor threading robust and memory efficient, I decided to implement a simple solution of bounded ThreadingMixin. A better candidate might seem to be a ThreadPoolExecutor, but it proved to be very memory hungry.
The reason for using threads in the first place is:
The ideal solution would be to get right of our rigid in-house implementation based on BaseServer and etither