Bug 33600: `max_pending_results` is not directly used in `main_loop`

3cbba222 · Georg Koppen · juga · e361caf8 · 3cbba222
Commit 3cbba222 authored Mar 11, 2020 by Georg Koppen Committed by juga Mar 21, 2020
Hide whitespace changes
Inline Side-by-side

Showing with 2 additions and 3 deletions

sbws/core/scanner.py sbws/core/scanner.py +2 -3

No files found.
--- a/sbws/core/scanner.py
+++ b/sbws/core/scanner.py
@@ -460,7 +460,7 @@ def result_putter_error(target):
 def main_loop(args, conf, controller, relay_list, circuit_builder, result_dump,
-              relay_prioritizer, destinations, max_pending_results, pool):
+              relay_prioritizer, destinations, pool):
    """Starts and reuse the threads that measure the relays forever.
    It starts a loop that will be run while there is not and event signaling
@@ -701,8 +701,7 @@ def run_speedtest(args, conf):
    max_pending_results = conf.getint('scanner', 'measurement_threads')
    pool = Pool(max_pending_results)
    try:
-        main_loop(args, conf, controller, rl, cb, rd, rp, destinations,
+        main_loop(args, conf, controller, rl, cb, rd, rp, destinations, pool)
-                  max_pending_results, pool)
    except KeyboardInterrupt:
        log.info("Interrupted by the user.")
        stop_threads(signal.SIGINT, None)