Andrew Wong has uploaded this change for review. ( http://gerrit.cloudera.org:8080/11836
Change subject: revert change to exactly_once_writes-itest ...................................................................... revert change to exactly_once_writes-itest Since 5894af6ff12291ffab2d3304b34f77fe6d112771, in some environments, exactly_once_writes-itest will pass successfully but report a leak that would not fail the test itself. Try as I might to get to the bottom of the non-fatal leak, its root cause has evaded me. So instead, I'm reverting the test change that led to its leakiness. It seems it only fails some of the time when running a full ctest suite locally (i.e. not through dist-test). Some conclusions I've drawn about the leak: * Not easily reproducible via dist-test, even if we begin reporting LeakSanitizer errors on passing tests (which we don't today) * Not easily reproducible when running the test locally on its own * Not deterministically reproducible when running a full ctest suite locally Without the change, the leak was detected in 2/7 runs of the full test suite, and with the change, in 0/14. Change-Id: If4091d3905d871acb48ec4d88c7b81ee48bf0eed --- M src/kudu/integration-tests/exactly_once_writes-itest.cc 1 file changed, 2 insertions(+), 13 deletions(-) git pull ssh://gerrit.cloudera.org:29418/kudu refs/changes/36/11836/1 -- To view, visit http://gerrit.cloudera.org:8080/11836 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-Project: kudu Gerrit-Branch: master Gerrit-MessageType: newchange Gerrit-Change-Id: If4091d3905d871acb48ec4d88c7b81ee48bf0eed Gerrit-Change-Number: 11836 Gerrit-PatchSet: 1 Gerrit-Owner: Andrew Wong <[email protected]>
