-
- Downloads
Yet another attempt to fix unstability of prover answers
- Call_provers.parse_prover_run does not attempt fixing answer anymore, except in the case where the answer is HighFailure and time is close to time limit (which is considered as Timeout) - Session_scheduler.fuzzy_proof_time is now more liberal, accepts that two answers Unknown or Timeout of OutOfMemory with less than 10% difference in time are equivalent, and thus should not be reported as a significant change
Showing
- examples/bts/fsetint/why3session.xml 16 additions, 16 deletionsexamples/bts/fsetint/why3session.xml
- examples/check-builtin/int/why3session.xml 19 additions, 19 deletionsexamples/check-builtin/int/why3session.xml
- examples/knuth_prime_numbers/why3session.xml 33 additions, 42 deletionsexamples/knuth_prime_numbers/why3session.xml
- examples/logic/bitvectors/why3session.xml 50 additions, 50 deletionsexamples/logic/bitvectors/why3session.xml
- examples/logic/einstein/why3session.xml 55 additions, 50 deletionsexamples/logic/einstein/why3session.xml
- examples/tests-provers/div/why3session.xml 196 additions, 196 deletionsexamples/tests-provers/div/why3session.xml
- examples/tests-provers/div_real/why3session.xml 11 additions, 4 deletionsexamples/tests-provers/div_real/why3session.xml
- src/driver/call_provers.ml 45 additions, 10 deletionssrc/driver/call_provers.ml
- src/session/session_scheduler.ml 11 additions, 3 deletionssrc/session/session_scheduler.ml
Loading
Please register or sign in to comment