-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
2018 Week 39-41
-
5
-
NEW
-
NEW
With multithreaded incremental solving together with DRL we sometimes get this:
Caused by: java.lang.IllegalStateException: Score corruption:
the workingScore (-471init/0hard/-10soft) is not
the uncorruptedScore (-471init/0hard/0soft) after completedAction (...):
Score corruption analysis could not be generated because either corrupted constraintMatchEnabled (false) or uncorrupted constraintMatchEnabled (true) is disabled.
Check your score constraints manually.
Caused by: java.lang.IllegalStateException: Score corruption:
the workingScore (-257init/0hard/0soft) is not
the uncorruptedScore (-257init/-1hard/0soft) after completedAction (...):
The corrupted scoreDirector has no ConstraintMatch(s) which are in excess.
The corrupted scoreDirector has no ConstraintMatch(s) which are missing.
The corrupted scoreDirector has no ConstraintMatch(s) in excess or missing. That could be a bug in this class (class org.optaplanner.core.impl.score.director.drools.DroolsScoreDirector).
Check your score constraints.
- is related to
-
PLANNER-1318 Full assert should check if the move thread's state (genuine variables + shadow variables) is the same as the solver's state
-
- Open
-