$ make -j -s install
    ...
    --- subprocess32, Linux only
    /bin/sh: line 3: [: =: unary operator expected
    --- stream
    ...
    Greenplum Database installation complete.

When `$(BLD_ARCH)` is empty, the check becomes `[ = 'aix7_ppc_64' ]`, and gets
the unary operator expected error.

1. copy *test/regress/*.pm file to install locaiton to support
regression test diff
2. set LIBPATH and GP_LIBPATH_FOR_PYTHON env for AIX
Signed-off-by: NPeifeng Qiu <pqiu@pivotal.io>

1. Add dependency packages to Ivy
2. Modify set_bld_arch.sh to correctly recongize aix7
3. Disable unsupported python libraries on aix7.
4. Disable gpmapreduce for aix7
5. Set ADDON_DIR for aix7
   Signed-off-by: Peifeng Qiu pqiu@pivotal.io

Previously, the "all" target was used only by gpMgmt/bin/Makefile in
place of the "install" target used elsewhere. The underlying reason was
because python doesn't need a compile phase (the "all" target).

However, this is inconsistent. Change to use the standard "install"
target, which is also the default on the gpMgmt/bin/Makefile.
Signed-off-by: NLarry Hamel <lhamel@pivotal.io>

-- metadata about gucs, like GUC_DISALLOW_IN_FILE, is not available via
sql. Work around that by parsing the C code that defines this metadata, and store
relevant information in a file, to be read by gpconfig when called to
change a GUC.

-- the Makefile in gpMgmt/bin will create a local file during 'make install', used by
gpconfig to validate that a given GUC can be changed
Signed-off-by: NC.J. Jameson <cjameson@pivotal.io>
Signed-off-by: NShoaib Lari <slari@pivotal.io>
Signed-off-by: NNadeem Ghani <nghani@pivotal.io>
Signed-off-by: NMarbin Tan <mtan@pivotal.io>

Since python 2.7 has the unittest module included, we do not need to use
unittest2 anymore. This removes this dependency requirement. We
previously used the unittest2 module as it included features that were
not present in python 2.6. There are still unittest2 dependencies in the
TINC tests, but that may be a more intensive effort.

The old cdbfast test suite had these, good to move to ICW.

Signed-off-by: NMarbin Tan <mtan@pivotal.io>

* Fixing a hardcoded python library path that may not be valid for other
  python version.
Signed-off-by: NMarbin Tan <mtan@pivotal.io>

We added make commands to clean up files that are gitignored, because
now git clean won't be able to delete them.
Signed-off-by: NMarbin Tan <mtan@pivotal.io>

* Enable to run behave tests with the installed binary instead of source
* code.

-- change PYTHONPATH priority for src/ext, putting it behind
installed/ext

Signed-off-by: NDavid Sharp <dsharp@pivotal.io>

to the OS, if you had versions built using vagrant that were not
compatible with your OS this would fail

Throttle the vagrants to 50%

Build gpdb on debian as the vagrant user. The root user will fail
to change the uid/gid on the nfs mount

Running make install is expected to produce lots of output but we
perform some steps that can be removed and have some level of
printing to STDOUT that is superflous. Suppress output for logic
with @ and remove unused commands and filetypes (perforce and CVS).

* new "unitdevel" target uses whatever libraries and python is provided by developer's PATH
* that new "unitdevel" target allows whatever logging that the unit tests output, to stdout
* change names of 4 "unit" test files that actually require a cluster to be running to have "_cluster_" in their names
* keep the behavior of the existing "make check" to run both pure unit tests AND the "_cluster_" tests

This commit represents a major overhaul of the backup and restore test suite,
with the following main goals:
1) Cut down the time required to run the tests (previous runtime was ~3.5 hours
on Pivotal test machines, now it's down to around 1 hour 15 minutes).
2) Make each test scenario independent, so that the database state at the start
of a scenario does not depend on which scenarios were run before it and failures
in one scenario will not cause later scenarios to fail as a result.
3) Group commonly used steps, remove redundant scenarios and unnecessary steps
within scenarios, standardize common database and table names, and perform
similar cleanup, both to cut down on runtime and to improve readability and
comprehensibility of the suite.