dance858 / PSLP / 33340046429

76%

push

github

Respect verbose=false in print_infeas_or_unbnd_message (#55)

run_presolver() gates every other console message behind
stgs->verbose (print_start_message, print_end_message), but calls
print_infeas_or_unbnd_message() unconditionally when the problem is
detected infeasible or unbounded. A caller that sets verbose = false
to keep PSLP silent still gets "PSLP declares problem as infeasible."
printed directly to stdout for exactly that case.

Found while embedding PSLP in cuOpt's Java bindings
(github.com/NVIDIA/cuopt): the caller already sets verbose = false,
but this one unconditional printf writes directly to the process's
native stdout stream, which corrupts tooling that intercepts stdout
for its own purposes -- in our case, Maven Surefire's forked-JVM
communication protocol.

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>

2686 of 4450 branches covered (60.36%)

Branch coverage included in aggregate %.

2 of 2 new or added lines in 1 file covered. (100.0%)

4359 of 4857 relevant lines covered (89.75%)

5607.92 hits per line