AlgBench will not notice an interrupt if the interrrupt was handled by a native extension (like Gurobi)

[d-krupke]

There is a problem with bad entries when interrupting the benchmark via ctrl+c. Solvers like Gurobi and CP-SAT handle the signal on their own and stop the search but do not interrupt the Python-interpreter. Thus, they just terminate early and create bad entries (essentially, your shortened the time limit for this entry).

Check if there is some way to find out if ctrl+c was pressed during the creation of an entry.