From a30140b1e5e270606c7e53db96d81ecbfba6d7d5 Mon Sep 17 00:00:00 2001 From: Andres Noetzli Date: Sat, 14 Apr 2018 01:28:17 -0700 Subject: [PATCH] Fix get-unsat-core detection in regression script (#1773) Due to a typo in the regression script, the (get-unsat-core) command was not recognized (the script was looking for (get-unsat-cores)), so it tried to run a regression script containing (get-unsat-core) even when CVC4 was compiled without proof support. This commit fixes the typo. --- test/regress/run_regression.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/regress/run_regression.py b/test/regress/run_regression.py index 1e3848338..3b97f6dde 100755 --- a/test/regress/run_regression.py +++ b/test/regress/run_regression.py @@ -187,7 +187,7 @@ def run_regression(proof, dump, wrapper, cvc4_binary, benchmark_path): # been set explicitly, the benchmark is invalid. sys.exit('Cannot determine status of "{}"'.format(benchmark_path)) - if not proof and ('(get-unsat-cores)' in metadata_content + if not proof and ('(get-unsat-core)' in metadata_content or '(get-unsat-assumptions)' in metadata_content): print( '1..0 # Skipped: unsat cores not supported without proof support') -- 2.30.2