When life gets too hard for the solver, it'll raise an UnknownSatisfiability error, and then there's a good chance that our argument realization code produce the same exception, failing to find concrete values for the draws. We probably need to extend the solver timeout during realization and/or wipe the solver state and pretend it was a useless/trivial iteration.
This is the root cause of hypothesis test failures like returning a symbolic type from provider.realize(obj) (comment, CI)
When life gets too hard for the solver, it'll raise an UnknownSatisfiability error, and then there's a good chance that our argument realization code produce the same exception, failing to find concrete values for the draws. We probably need to extend the solver timeout during realization and/or wipe the solver state and pretend it was a useless/trivial iteration.
This is the root cause of hypothesis test failures like
returning a symbolic type from provider.realize(obj)
(comment, CI)