[jira] [Commented] (HBASE-14201) hbck should not take a lock unless fixing errors

2015-08-12 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-14201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14694334#comment-14694334 ] Hudson commented on HBASE-14201: FAILURE: Integrated in HBase-1.2 #103 (See [https://bui

[jira] [Commented] (HBASE-14201) hbck should not take a lock unless fixing errors

2015-08-12 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-14201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14694260#comment-14694260 ] Hudson commented on HBASE-14201: FAILURE: Integrated in HBase-1.3-IT #85 (See [https://b

[jira] [Commented] (HBASE-14201) hbck should not take a lock unless fixing errors

2015-08-12 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-14201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14694259#comment-14694259 ] Hudson commented on HBASE-14201: FAILURE: Integrated in HBase-1.3 #103 (See [https://bui

[jira] [Commented] (HBASE-14201) hbck should not take a lock unless fixing errors

2015-08-12 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-14201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14694244#comment-14694244 ] Hudson commented on HBASE-14201: FAILURE: Integrated in HBase-1.2-IT #86 (See [https://b

[jira] [Commented] (HBASE-14201) hbck should not take a lock unless fixing errors

2015-08-12 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-14201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14694225#comment-14694225 ] Hudson commented on HBASE-14201: FAILURE: Integrated in HBase-TRUNK #6719 (See [https://

[jira] [Commented] (HBASE-14201) hbck should not take a lock unless fixing errors

2015-08-12 Thread Elliott Clark (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-14201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14694001#comment-14694001 ] Elliott Clark commented on HBASE-14201: --- Nope everything looks good. The -1's usual

[jira] [Commented] (HBASE-14201) hbck should not take a lock unless fixing errors

2015-08-11 Thread Simon Law (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-14201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14692665#comment-14692665 ] Simon Law commented on HBASE-14201: --- Er, I don't see the failing test. Is this because

[jira] [Commented] (HBASE-14201) hbck should not take a lock unless fixing errors

2015-08-11 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-14201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14692647#comment-14692647 ] Hadoop QA commented on HBASE-14201: --- {color:red}-1 overall{color}. Here are the result

[jira] [Commented] (HBASE-14201) hbck should not take a lock unless fixing errors

2015-08-11 Thread Simon Law (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-14201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14692384#comment-14692384 ] Simon Law commented on HBASE-14201: --- Hmm, looks like it failed on parallel hbck testing

[jira] [Commented] (HBASE-14201) hbck should not take a lock unless fixing errors

2015-08-11 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-14201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14692364#comment-14692364 ] Hadoop QA commented on HBASE-14201: --- {color:red}-1 overall{color}. Here are the result

[jira] [Commented] (HBASE-14201) hbck should not take a lock unless fixing errors

2015-08-11 Thread Elliott Clark (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-14201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14682309#comment-14682309 ] Elliott Clark commented on HBASE-14201: --- lgtm lets see what that QA bot has to say.