Open will62794 opened 3 years ago
Note: When using Z3 as a backend solver, I believe this can be worked around by manually specifying a timeout in the Z3 arguments e.g. giving a timeout of 100 milliseconds:
tlapm --toolbox 0 0 --printallobs --debug tempfiles --method smt --solver 'z3 -t:100 -smt2 "$file"' --nofp --stretch 0.1 MongoRaftReconfig_TautCheck.tla
When using the
--stretch
parameter oftlapm
, the resulting timeouts for the backend solvers don't seem to respected properly. See the following output from the attached repro (tlapm-timeout-repro.zip):The last obligation status message printed reports the following:
which seems that it violated the allowed timeout budget. My understanding is that Z3, for example, can directly handle millisecond timeout values e.g.
so it's unclear why this timeout is not being respected properly