Commit 58ffe141 authored by Peter Eisentraut's avatar Peter Eisentraut

Revert "Add basic TAP test setup for pg_upgrade"

This reverts commit f41e56c7.

The build farm client would run the pg_upgrade tests twice, once as part
of the existing pg_upgrade check run and once as part of picking up all
TAP tests by looking for "t" directories.  Since the pg_upgrade tests
are pretty slow, we will need a better solution or possibly a build farm
client change before we can proceed with this.
parent 791961f5
...@@ -36,9 +36,8 @@ clean distclean maintainer-clean: ...@@ -36,9 +36,8 @@ clean distclean maintainer-clean:
pg_upgrade_dump_globals.sql \ pg_upgrade_dump_globals.sql \
pg_upgrade_dump_*.custom pg_upgrade_*.log pg_upgrade_dump_*.custom pg_upgrade_*.log
check: test.sh check: test.sh all
$(prove_check)
MAKE=$(MAKE) bindir=$(bindir) libdir=$(libdir) EXTRA_REGRESS_OPTS="$(EXTRA_REGRESS_OPTS)" $(SHELL) $< --install MAKE=$(MAKE) bindir=$(bindir) libdir=$(libdir) EXTRA_REGRESS_OPTS="$(EXTRA_REGRESS_OPTS)" $(SHELL) $< --install
installcheck: # installcheck is not supported because there's no meaningful way to test
$(prove_installcheck) # pg_upgrade against a single already-running server
use strict;
use warnings;
use TestLib;
use Test::More tests => 8;
program_help_ok('pg_upgrade');
program_version_ok('pg_upgrade');
program_options_handling_ok('pg_upgrade');
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment