Closed matbesancon closed 3 years ago
That's strange, a SCIP bugfix release shouldn't change the behavior w.r.t. callbacks, right?
If I remember correctly, the NeverSatisfied
constraint handler simply has a CHECK
callback that always returns false
.
Maybe the new SCIP has some kind of "shortcut" where the infeasibility of the overall problem can be decided without ever calling the ENFORCE
method.
EDIT: That is to say: maybe the assumptions that the test makes are too strong. As long as the resulting status is Infeasible
, and either CHECK
or ENFORCE
is called at least once, it seems to be correct?!
That's strange, a SCIP bugfix release shouldn't change the behavior w.r.t. callbacks, right?
not really. In that case it did, just in the case when there are no variables left after presolving.
Closed by enforcing the SCIP version now, and adapted the test in the #195 PR
I cross-posted this issue on the SCIP repo:
on SCIP
v7.0.3
,@test ch.enfo_called == 1
fails with 0 on the left-hand side@rschwarz do you know if something in the NSCH handler could break?