hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10410) On some JREs, hbase-server is failing due to "timeout" without any test actually timing out
Date Thu, 23 Jan 2014 23:02:38 GMT

    [ https://issues.apache.org/jira/browse/HBASE-10410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13880490#comment-13880490
] 

Andrew Purtell commented on HBASE-10410:
----------------------------------------

Hmm

{noformat}
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.16:test (secondPartTestsExecution)
on project hbase-server: Execution secondPartTestsExecution of goal org.apache.maven.plugins:maven-surefire-plugin:2.16:test
failed: Fork mode perThread is not a legal value -> [Help 1]
{noformat}


> 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)

Mime
View raw message