What's the issue?
In SolverTest the check_solution_invariants method compares the coreset to the result of a call to solver.reduce or solver.refine. The passed coreset may have been computed with jit_variant(solver.reduce) while the call in check_solution_invariants is always computed without JIT transformation. However, we cannot be sure that jit_variant(solver.reduce)(...) == solver.reduce(...), due to slight numerical differences that can manifest from JIT transformation. While this doesn't cause us any problems at the moment, it could be a source of future (device dependent) test failures.
What's the issue?
In
SolverTestthecheck_solution_invariantsmethod compares the coreset to the result of a call tosolver.reduceorsolver.refine. The passed coreset may have been computed withjit_variant(solver.reduce)while the call incheck_solution_invariantsis always computed without JIT transformation. However, we cannot be sure thatjit_variant(solver.reduce)(...) == solver.reduce(...), due to slight numerical differences that can manifest from JIT transformation. While this doesn't cause us any problems at the moment, it could be a source of future (device dependent) test failures.