[
https://issues.apache.org/jira/browse/KUDU-3615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17888313#comment-17888313
]
ASF subversion and git services commented on KUDU-3615:
-------------------------------------------------------
Commit 446861c68cb3cc5e8ef8caaadf7d8eefc2ec1387 in kudu's branch
refs/heads/master from Alexey Serbin
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=446861c68 ]
[security-itest] stop polluting TEST_TMPDIR with logs
By default, KuduTest-based scenarios have their FLAGS_log_dir pointed to
the TEST_TMPDIR directory, so if master/tserver is run using the
"kudu master run"/"kudu tserver run" CLI tool, the generated log files
aren't cleaned up. This patch addresses the issue by customizing the
--log_dir flag to keep all the logs under the test's directory which
is automatically removed once the scenario successfully completes.
This patch addresses KUDU-3615, at least partially.
Change-Id: Ib70b8a477beeab82af0ee6b4099114d5482f12cf
Reviewed-on: http://gerrit.cloudera.org:8080/21909
Tested-by: Alexey Serbin <ale...@apache.org>
Reviewed-by: KeDeng <kdeng...@gmail.com>
> Investigate /tmp/kudutest cleanup in tests
> ------------------------------------------
>
> Key: KUDU-3615
> URL: https://issues.apache.org/jira/browse/KUDU-3615
> Project: Kudu
> Issue Type: Task
> Components: infra
> Reporter: Marton Greber
> Priority: Minor
> Attachments: log.txt
>
>
> In https://gerrit.cloudera.org/#/c/21634/ build-and-test run, in debug mode
> there was an error that /tmp/kudutest-1000/minicluster-data was full.
> The task is to investigate how these dirs are cleaned up, to check if it was
> a fluke or there is some cleanup we should do.
> Attached the full log for the failed run.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
