You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2014/01/24 00:24:38 UTC

[jira] [Resolved] (HBASE-10410) On some JREs, hbase-server is failing due to "timeout" without any test actually timing out

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

Andrew Purtell resolved HBASE-10410.
------------------------------------

    Resolution: Invalid

With Surefire 2.16 and some POM hacks, I've found a real culprit.

> On some JREs, hbase-server is failing due to "timeout" without any test actually timing out
> -------------------------------------------------------------------------------------------
>
>                 Key: HBASE-10410
>                 URL: https://issues.apache.org/jira/browse/HBASE-10410
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.98.0
>            Reporter: Andrew Purtell
>
> This is frustrating. On some JREs (Java 7) I am seeing hbase-server fail due to timeout, without any test actually reporting a timeout.  This StackOverflow answer talks about how JUnit < 4.12-SNAPSHOT may report a timeout if the test throws an InterruptedException: http://stackoverflow.com/questions/17016011/junit-test-times-out-despite-executing-quickly  Those happen at various points when shutting down the minicluster. We may be letting one escape. 



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)