Either the test is flaky, or it shows a race condition in the SolverManager:

The test expects the score to be feasible and fails despite the fact that the log shows (see the attachment) the 0 hard score has been attained.