[ https://issues.apache.org/jira/browse/HBASE-13561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14617470#comment-14617470 ]
Hudson commented on HBASE-13561: -------------------------------- SUCCESS: Integrated in HBase-1.3-IT #26 (See [https://builds.apache.org/job/HBase-1.3-IT/26/]) HBASE-13561 ITBLL.Verify doesn't actually evaluate counters after job completes (Josh Elser) (stack: rev 4e84ac7924a4f09be05c57ec018c796b960d3760) * hbase-it/src/test/java/org/apache/hadoop/hbase/test/IntegrationTestBigLinkedList.java > ITBLL.Verify doesn't actually evaluate counters after job completes > ------------------------------------------------------------------- > > Key: HBASE-13561 > URL: https://issues.apache.org/jira/browse/HBASE-13561 > Project: HBase > Issue Type: Bug > Components: integration tests > Affects Versions: 1.0.0, 2.0.0, 1.1.0, 0.98.12 > Reporter: Josh Elser > Assignee: Josh Elser > Fix For: 2.0.0, 1.1.2, 1.3.0, 1.2.1 > > Attachments: HBASE-13561-v1.patch, HBASE-13561-v2.patch > > > Was digging through ITBLL and noticed this oddity: > The {{Verify}} Tool doesn't actually call {{Verify#verify(long)}} like the > {{Loop}} Tool does. Granted, it doesn't know the total number of KVs that > were written given the current arguments, it's not even checking to see if > there things like UNDEFINED records found. > It seems to me that {{Verify}} should really be doing *some* checking on the > counters like {{Loop}} does and not just leaving it up to the visual > inspection of whomever launched the task. > Am I missing something? -- This message was sent by Atlassian JIRA (v6.3.4#6332)