From 24f129a63b395a13ba10a05ff128e8e27ba75ed5 Mon Sep 17 00:00:00 2001 From: Andres Noetzli Date: Tue, 8 Oct 2019 23:24:42 -0700 Subject: 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. --- test/regress/regress0/parser/force_logic_success.smt2 | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 test/regress/regress0/parser/force_logic_success.smt2 (limited to 'test/regress/regress0') 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) -- cgit v1.2.3