[2/2] kudu git commit: [build] add -D{LEAK,UNDEFINED}_SANITIZER

2018-08-27 Thread granthenke
[build] add -D{LEAK,UNDEFINED}_SANITIZER To enable __lsan_default_suppressions() defined in src/kudu/util/sanitizer_options.cc, it's necessary to have LEAK_SANITIZER macro enabled during the compilation. Also, defined UNDEFINED_SANITIZER macro to compile-in __ubsan_default_options() as well.

[1/2] kudu git commit: util: add once class based on std::call_once

2018-08-27 Thread granthenke
Repository: kudu Updated Branches: refs/heads/master bb78520a7 -> 3bb5f56cf util: add once class based on std::call_once The existing KuduOnceDynamic class only allows calling functions of type Status(void). I intend on adding an argument to some of the existing the Status(void) methods that

kudu-site git commit: Publish commit(s) from site source repo: 1488e1788 [site] Add descriptions to the DOAP file

2018-08-27 Thread abukor
Repository: kudu-site Updated Branches: refs/heads/asf-site 23296c046 -> 04c5e1769 Publish commit(s) from site source repo: 1488e1788 [site] Add descriptions to the DOAP file Site-Repo-Commit: 1488e1788de96e34ff4970e802a5cab630b69099 Project:

[1/3] kudu git commit: [kudu-backup] fix tests

2018-08-27 Thread granthenke
Repository: kudu Updated Branches: refs/heads/master 0dc19bfb3 -> f5ffcb4d7 [kudu-backup] fix tests - Previously TestKuduBackup class wasn't executed in ./gradlew test, ./gradlew :kudu-backup:test, mvn test, ... - TestKuduBackup#testRandomBackupAndRestore was failed in a column of

kudu git commit: [site] Add descriptions to the DOAP file

2018-08-27 Thread granthenke
Repository: kudu Updated Branches: refs/heads/gh-pages e86c4bda6 -> 1488e1788 [site] Add descriptions to the DOAP file Change-Id: I77cf9e780e49a9e475df11cdebffeee1e02bc9a9 Reviewed-on: http://gerrit.cloudera.org:8080/11287 Tested-by: Grant Henke Reviewed-by: Grant Henke Project:

[2/3] kudu git commit: build-and-test: export EXTRA_GRADLE_FLAGS

2018-08-27 Thread granthenke
build-and-test: export EXTRA_GRADLE_FLAGS build-and-test.sh generates a list of flags with which to configure gradle. Unless these configurations are `export`ed, they won't be visible in other processes, e.g. when running dist_test.py. Notably, this would result in dist_test.py calling gradlew