Hello Kudu Jenkins,
I'd like you to reexamine a change. Please visit
http://gerrit.cloudera.org:8080/5203
to look at the new patch set (#3).
Change subject: dist-test: set TEST_TMPDIR inside test directory
......................................................................
dist-test: set TEST_TMPDIR inside test directory
Recently I hit a case where I had a test which was crashing with an ASAN
warning halfway through, after writing a bunch of data into the test
tmpdir. Because we weren't setting TEST_TMPDIR in the dist-test
environment, the leftover data ended up orphaned in /tmp/kudutest-1000,
which wasn't cleaned up after the dist-test task ended.
This just sets the tmpdir to be inside the root working directory of the
test, so that we are guaranteed to clean it up after the test finishes.
To verify, I submitted a job and looked at the resulting test logs, and
saw that it was now writing within the test directory instead of within
/tmp/
Change-Id: I0497591860f7e8b1ea18c1ee9b05becb282f6ec8
---
M build-support/run_dist_test.py
1 file changed, 5 insertions(+), 0 deletions(-)
git pull ssh://gerrit.cloudera.org:29418/kudu refs/changes/03/5203/3
--
To view, visit http://gerrit.cloudera.org:8080/5203
To unsubscribe, visit http://gerrit.cloudera.org:8080/settings
Gerrit-MessageType: newpatchset
Gerrit-Change-Id: I0497591860f7e8b1ea18c1ee9b05becb282f6ec8
Gerrit-PatchSet: 3
Gerrit-Project: kudu
Gerrit-Branch: master
Gerrit-Owner: Todd Lipcon <[email protected]>
Gerrit-Reviewer: Adar Dembo <[email protected]>
Gerrit-Reviewer: Kudu Jenkins
Gerrit-Reviewer: Mike Percy <[email protected]>
