Proper cleanup of containerized tool-info module on early termination
Proper cleanup of containerized tool-info module on early termination

If we did not start benchmarking at all
(for example because tool was not found),
the call to benchmark.tool.close() was missing.
This meant that the multiprocessing pool for the tool-info module
was not closed and produced an ugly (but harmless) stack trace
on process termination.

ultimate-pa/benchexec,sosy-lab/benchexec,sosy-lab/benchexec,sosy-lab/benchexec,dbeyer/benchexec,sosy-lab/benchexec,ultimate-pa/benchexec,dbeyer/benchexec,ultimate-pa/benchexec,sosy-lab/benchexec,ultimate-pa/benchexec,dbeyer/benchexec,ultimate-pa/benchexec,ultimate-pa/benchexec,sosy-lab/benchexec,dbeyer/benchexec