Alexey Serbin has uploaded this change for review. ( http://gerrit.cloudera.org:8080/18027
Change subject: [tests] don't use client-stress-test in ASAN/TSAN builds ...................................................................... [tests] don't use client-stress-test in ASAN/TSAN builds Test scenarios in client-stress-test are CPU and memory intensive, and some of those are intended for benchmarking to track performance regressions in the C++ client's metacache. With that, there isn't much sense to build and run them for ASAN/TSAN builds, so why to compile them under ASAN/TSAN configurations at all? As for the test coverage to catch possible concurrency and undefined behavior issues, there is overlap between the tests in client-stress-test and tests in client-test, master-stress-test, and many others. The motivation for this change is to address the feedback for one of prior changelists [1]. [1] https://gerrit.cloudera.org/#/c/18024/3/src/kudu/integration-tests/client-stress-test.cc@337 Change-Id: Ic044d051d6011d1cca95fc92d1daf400e3e3d116 --- M src/kudu/integration-tests/CMakeLists.txt M src/kudu/integration-tests/client-stress-test.cc 2 files changed, 6 insertions(+), 13 deletions(-) git pull ssh://gerrit.cloudera.org:29418/kudu refs/changes/27/18027/1 -- To view, visit http://gerrit.cloudera.org:8080/18027 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-Project: kudu Gerrit-Branch: master Gerrit-MessageType: newchange Gerrit-Change-Id: Ic044d051d6011d1cca95fc92d1daf400e3e3d116 Gerrit-Change-Number: 18027 Gerrit-PatchSet: 1 Gerrit-Owner: Alexey Serbin <[email protected]>
