You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Chris Nauroth (JIRA)" <ji...@apache.org> on 2015/10/27 22:54:27 UTC

[jira] [Updated] (HADOOP-12519) hadoop-azure tests create a metrics configuration file in the module root directory.

     [ https://issues.apache.org/jira/browse/HADOOP-12519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Nauroth updated HADOOP-12519:
-----------------------------------
    Attachment: HADOOP-12519.001.patch

The attached patch moves the metrics configuration file into target/test-classes, so it's still available on the runtime classpath for tests, but it doesn't dirty the workspace.  This is the same approach used by hadoop-common tests, like {{TestMetricsSystemImpl}}.

> hadoop-azure tests create a metrics configuration file in the module root directory.
> ------------------------------------------------------------------------------------
>
>                 Key: HADOOP-12519
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12519
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: azure, test
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>            Priority: Minor
>         Attachments: HADOOP-12519.001.patch
>
>
> The hadoop-azure JUnit tests create a metrics configuration file.  This file gets saved in the root directory of the hadoop-azure module.  This dirties the git workspace and won't get removed by {{mvn clean}}, because it's outside of the build target directory.  It also can cause the pre-commit license check step to fail, because this ends up looking like the patch added a new file without the Apache license header.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)