From 6eccdbdcda0573dda1874ab00efa12255f606748 Mon Sep 17 00:00:00 2001 From: Jelte Fennema Date: Wed, 5 Apr 2023 13:53:21 +0200 Subject: [PATCH] Fix running PG upgrade tests with run_test.py In #6814 we started using the Python test runner for upgrade tests in run_test.py, instead of the Perl based one. This had a problem though, not all tests in minimal_schedule can be run with the Python runner. This adds a separate minimal schedule for the pg_upgrade tests which doesn't include the tests that break with the Python runner. --- src/test/regress/citus_tests/run_test.py | 2 +- src/test/regress/minimal_pg_upgrade_schedule | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) create mode 100644 src/test/regress/minimal_pg_upgrade_schedule diff --git a/src/test/regress/citus_tests/run_test.py b/src/test/regress/citus_tests/run_test.py index 24a9d8b3671..4657114a3ae 100755 --- a/src/test/regress/citus_tests/run_test.py +++ b/src/test/regress/citus_tests/run_test.py @@ -239,7 +239,7 @@ def default_base_schedule(test_schedule, args): return None if "pg_upgrade" in test_schedule: - return "minimal_schedule" + return "minimal_pg_upgrade_schedule" if test_schedule in ARBITRARY_SCHEDULE_NAMES: print(f"WARNING: Arbitrary config schedule ({test_schedule}) is not supported.") diff --git a/src/test/regress/minimal_pg_upgrade_schedule b/src/test/regress/minimal_pg_upgrade_schedule new file mode 100644 index 00000000000..64e5c982da5 --- /dev/null +++ b/src/test/regress/minimal_pg_upgrade_schedule @@ -0,0 +1 @@ +test: multi_test_helpers multi_test_helpers_superuser multi_test_catalog_views