Skip to content

G
Gpdb

Greenplum / Gpdb

通知 7
Star 1
Fork 0
G
Gpdb

前往新版Gitcode，体验更适合开发者的 AI 搜索 >>

切换分支/标签
  1. 20 7月, 2020 1 次提交
  3. 19 5月, 2020 1 次提交
    • K
      add GPDB 6X centos7 FIPS python regression test · 1bb9ce2c
      由 Kalen Krempely 提交于 
      For Greenplum 6X on centos7 in a FIPS enabled environment our python
utilities would log the following error.

ERROR:root:code for hash md5 was not found.
Traceback (most recent call last):
  File "/usr/local/greenplum-db-devel/ext/python/lib/python2.7/hashlib.py", line 147, in <module>
    globals()[__func_name] = __get_hash(__func_name)
  File "/usr/local/greenplum-db-devel/ext/python/lib/python2.7/hashlib.py", line 109, in __get_openssl_constructor
    return __get_builtin_constructor(name)
  File "/usr/local/greenplum-db-devel/ext/python/lib/python2.7/hashlib.py", line 97, in __get_builtin_constructor
    raise ValueError('unsupported hash type ' + name)
ValueError: unsupported hash type md5

This adds a regression test and was inspired from the following 5X
commit b07b2a23.
Co-authored-by: NMark Sliva <msliva@pivotal.io>
      1bb9ce2c
  5. 15 5月, 2020 1 次提交
    • B
      Update regexp pattern for python tarball · b486393e
      由 Bradford D. Boyle 提交于 
      The current python build artifact uses a semver pre-release segment to
encode build metadata (e.g, 2.7.12-build.42). This pattern does not work
well with the idea of post-release/revision numbers, where the revision
number is used to reflect additional deltas made on top of the upstream
version. As a concrete example, the version string `1.2.3+gp.4.build.5`
would indicate this is the fifth build of the binary artifact with four
modication/patches made to upstream version `1.2.3`.

The Greenplum Release Engineering team has update our build dependency
pipeline for python to use this post-release/revision number convention
and this PR updates the 6X_STABLE pipeline to consume these newer
artifacts.

[#172829377]
Authored-by: NBradford D. Boyle <bboyle@pivotal.io>
      b486393e
  7. 13 5月, 2020 1 次提交
  9. 09 4月, 2020 1 次提交
    • C
      Increase instance memory for gpexpand tests · dddd360b
      由 Chris Hajas 提交于 
      The gpepxand tests were going OOM with ORCA in debug build, as the
segments require more memory. Previously, ORCA was not being run in
debug build so this was not an issue. We've bumped up the instance from
n1-standard-2 to n1-standard-4, which doubles our memory from 7.5GB to
15GB.
      dddd360b
  11. 09 3月, 2020 1 次提交
  13. 03 2月, 2020 1 次提交
  15. 24 1月, 2020 1 次提交
  17. 17 1月, 2020 1 次提交
  19. 07 12月, 2019 1 次提交
  21. 30 10月, 2019 1 次提交
  23. 22 10月, 2019 1 次提交
    • B
      Move server-build publishing to a separate CI job · bad2466e
      由 Bradford D. Boyle 提交于 
      The `without_asserts` pipeline includes a time-based trigger which can
cause the pipeline to re-run the compilation jobs for the same commit.
When the compilation jobs attempt to re-`put` the server-build artifact,
the job fails because the build artifacts bucket is immutable.

This commit move the server-build publishing to a separate, hidden CI
job that does not block the release.
Authored-by: NBradford D. Boyle <bboyle@pivotal.io>
(cherry picked from commit aac2eeb9)
      bad2466e
  25. 19 10月, 2019 1 次提交
  27. 08 10月, 2019 1 次提交
  29. 24 9月, 2019 2 次提交
  31. 14 8月, 2019 1 次提交
  33. 13 8月, 2019 1 次提交
  35. 10 8月, 2019 1 次提交
  37. 23 7月, 2019 1 次提交
  39. 20 7月, 2019 1 次提交
  41. 17 7月, 2019 1 次提交
    • K
      CI: unvendor behave and install patchelf · b1eceb7a
      由 Kalen Krempely 提交于 
      This is a squashed manual cherry-pick of two commits. The first commit
358ce512 is:
CI: unvendor behave

To run behave tests, behave now needs to be installed in the PATH. The
correct version of behave can be installed with pip using

    pip install -r gpMgmt/requirements-dev.txt

For the CI tests, use virtualenv, which allows behave to be installed
while still using greenplum PYTHONPATH for our vendored python modules.
This is more of a problem for platforms like centos6 where the system
python is a different version than the vendored version.

The second commit e5e91bdc is:
behave: install patchelf to get around RPATH problems

Follow-up to the previous commit, which worked fine for CentOS6 but fell
apart with CentOS7.

Because our vendored Python doesn't contain an RPATH/RUNPATH pointer to
the location of its libpython, trying to execute it directly will result
in failures at link time. The previous commit took the approach that
greenplum_path.sh takes, which is to hardcode an LD_LIBRARY_PATH that
makes up for this bug. This approach works for CentOS6, which is running
Python 2.6 as its system version. On CentOS7, which has Python 2.7, the
LD_LIBRARY_PATH causes the system Python to use the vendored
libpython.so.2.7, and virtualenv fails.

Instead of forcing a cross-linking situation with LD_LIBRARY_PATH, fix
the problem in the vendored Python binary, by using patchelf to set up a
proper RUNPATH. (We originally tried to build our vendored Python with
an RPATH set at compile time, but the only way to do that without
knowing the eventual installation prefix is by setting a relative RPATH
using the `$ORIGIN` construct, and virtualenv is unfortunately
incompatible with that.) We do this on any platforms that provide a
patchelf binary, and do our best to limp along on all others.

Along the way, get rid of the run_behave.yml task, which has been
confusing us for the entirety of this work. CCP jobs now use
run_behave_on_ccp_cluster.yml consistently.
Co-authored-by: NNikolaos Kalampalikis <nkalampalikis@pivotal.io>
      b1eceb7a
  43. 16 7月, 2019 2 次提交
    • N
      gpexpand: Use larger instance_type for more memory · efdcd8c8
      由 Nikolaos Kalampalikis 提交于 
      After introducing sysctl settings in commit 42930ed1, gpexpand fails to
shutdown a segment with:
`'Shutdown failed! [Errno12] Cannot allocate memory'`

This is most likely due to the n1-standard-1 instance_type
having only 3.75 GB of memory, which is too small causing our python
utilities to fail when allocating multiple threads. This can be worked
around by setting the `-B` parallel_process option to a low value, or
setting the kernel parameter vm.overcommit_memory to 0. However, we
would like to test the standard sysctl settings as recommended to
customers, rather than supporting unrealistic edge cases such as
machines with very low memory.
Co-authored-by: NNikolaos Kalampalikis <nkalampalikis@pivotal.io>
(cherry picked from commit 6f494638)
      efdcd8c8
    • B
      Remove deprecated S3 resources for server RCs · 085c2e20
      由 Bradford D. Boyle 提交于 
      Release candidates for server and clients are stored in GCS and the S3
resources were deprecated four months ago. The S3 resources were left in
the pipeline to give downstream consumers an opportunity to update their
CI pipelines to use the new GCS resources. This commit finalizes the
deprecation of the S3 resources.
Authored-by: NBradford D. Boyle <bboyle@pivotal.io>
(cherry picked from commit 2c625e9a)
      085c2e20
  45. 12 7月, 2019 1 次提交
  47. 10 7月, 2019 1 次提交
  49. 02 7月, 2019 1 次提交
  51. 28 6月, 2019 1 次提交
  53. 27 6月, 2019 5 次提交
  55. 26 6月, 2019 1 次提交
  57. 25 6月, 2019 2 次提交
  59. 21 6月, 2019 1 次提交
  61. 09 6月, 2019 1 次提交
  63. 08 6月, 2019 1 次提交
  65. 05 6月, 2019 1 次提交