diff options
| author | Andres Noetzli <andres.noetzli@gmail.com> | 2019-10-08 23:24:42 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-10-08 23:24:42 -0700 |
| commit | 24f129a63b395a13ba10a05ff128e8e27ba75ed5 (patch) | |
| tree | 143ed7f10733c5db326ae17ec51b680ce7a8f4fa /test/regress/regress0 | |
| parent | 1d4c28c9211db363b716b33954644d200b91dfd8 (diff) | |
Avoid printing success for `--force-logic` (#3363)
CVC4 was printing success when `--force-logic` was used because
internally, `--force-logic` generates a `SetBenchmarkLogicCommand`. This
caused issues with the SMT-COMP trace executor. This commit fixes the
behavior by muting the command if it was not issued by the user.
The issue was likely introduced with #3062.
Diffstat (limited to 'test/regress/regress0')
| -rw-r--r-- | test/regress/regress0/parser/force_logic_success.smt2 | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/test/regress/regress0/parser/force_logic_success.smt2 b/test/regress/regress0/parser/force_logic_success.smt2 new file mode 100644 index 000000000..027d7ccc0 --- /dev/null +++ b/test/regress/regress0/parser/force_logic_success.smt2 @@ -0,0 +1,5 @@ +; COMMAND-LINE: --force-logic QF_BV --print-success +; EXPECT: success +; EXPECT: sat +(assert true) +(check-sat) |