[
https://issues.apache.org/jira/browse/HDFS-3132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13237014#comment-13237014
]
Tsz Wo (Nicholas), SZE commented on HDFS-3132:
----------------------------------------------
{quote}
There's not currently any easy way to run all the checks. And the problem with
splitting into sub-projects is that, often, a patch in Common would actually
break the build if it were committed before the associated patch in HDFS. I'd
rather chance introducing a few warnings than break the build for everyone.
{quote}
Agree. If splitting would break the build, it is better to commit together.
Buy why it is not easy to run the checks? I think it is easy at least to run
findbugs.
> Findbugs warning on HDFS trunk
> ------------------------------
>
> Key: HDFS-3132
> URL: https://issues.apache.org/jira/browse/HDFS-3132
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.24.0, 0.23.3
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Minor
> Attachments: hdfs-3132.txt
>
>
> "Inconsistent synchronization of
> org.apache.hadoop.hdfs.server.namenode.NameNode.state; locked 50% of time". I
> think this was probably one of my recent cross-project HA patches in which
> the QA bot was unable to run. Will investigate.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
