[ https://issues.apache.org/jira/browse/HBASE-8326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13632683#comment-13632683 ]
Hudson commented on HBASE-8326: ------------------------------- Integrated in hbase-0.95 #149 (See [https://builds.apache.org/job/hbase-0.95/149/]) HBASE-8326 mapreduce.TestTableInputFormatScan times out frequently (Nick Dimiduk) (Revision 1468224) Result = FAILURE tedyu : Files : * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/TableMapReduceUtil.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestTableInputFormatScan.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestTableInputFormatScan1.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestTableInputFormatScan2.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestTableInputFormatScanBase.java > mapreduce.TestTableInputFormatScan times out frequently > ------------------------------------------------------- > > Key: HBASE-8326 > URL: https://issues.apache.org/jira/browse/HBASE-8326 > Project: HBase > Issue Type: Bug > Components: mapreduce, test > Affects Versions: 0.98.0, 0.94.7, 0.95.1 > Reporter: Nick Dimiduk > Assignee: Nick Dimiduk > Fix For: 0.98.0, 0.94.7, 0.95.1 > > Attachments: HBASE-8326-reuse-jars-0.94-v0.patch, > HBASE-8326-reuse-jars-trunk-v0.patch, HBASE-8326-reuse-jars-trunk-v1.patch > > > bq. It looks like since this change > org.apache.hadoop.hbase.mapreduce.TestTableInputFormatScan has not passed a > single time in the EC2 builds (http://54.241.6.143/job/HBase-0.94/). Change > was introduced in Build #72, since then this tests times out (or doesn't > finish) > via [~lhofhansl] in [HBASE-8140 > comment|https://issues.apache.org/jira/browse/HBASE-8140?focusedCommentId=13629101&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13629101]. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira