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.

diff --git a/test/regress/run_regression.py b/test/regress/run_regression.py
index 1e38483385584a6678f41b06a9b3cf9d40b3a033..3b97f6dde017d7b7693a877c64880935b54891a3 100755 (executable)
--- 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')