You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2018/02/17 04:59:00 UTC
[jira] [Commented] (HBASE-20014) TestAdmin1 Times out
[ https://issues.apache.org/jira/browse/HBASE-20014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16368100#comment-16368100 ]
stack commented on HBASE-20014:
-------------------------------
.001 Pushed to master and branch-2.
Leaving open to see if fixes this one.
> TestAdmin1 Times out
> --------------------
>
> Key: HBASE-20014
> URL: https://issues.apache.org/jira/browse/HBASE-20014
> Project: HBase
> Issue Type: Sub-task
> Reporter: stack
> Priority: Major
> Attachments: HBASE-20014.branch-2.001.patch
>
>
> TestAdmin1 has 28+ tests. Nightly #336 shows this:
> {code}
> [ERROR] Tests run: 27, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 575.102 s <<< FAILURE! - in org.apache.hadoop.hbase.client.TestAdmin1
> [ERROR] org.apache.hadoop.hbase.client.TestAdmin1 Time elapsed: 1.134 s <<< ERROR!
> org.junit.runners.model.TestTimedOutException: test timed out after 600 seconds
> at org.apache.hadoop.hbase.client.TestAdmin1.testTableExist(TestAdmin1.java:899)
> [ERROR] testTableExist(org.apache.hadoop.hbase.client.TestAdmin1) Time elapsed: 1.134 s <<< ERROR!
> java.io.InterruptedIOException: Interrupt while waiting on Operation: CREATE, Table Name: default:testTableExist
> at org.apache.hadoop.hbase.client.TestAdmin1.testTableExist(TestAdmin1.java:899)
> [ERROR] org.apache.hadoop.hbase.client.TestAdmin1 Time elapsed: 0.022 s <<< ERROR!
> java.lang.Exception: Appears to be stuck in thread RS-EventLoopGroup-5-4
> [ERROR] Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 576.783 s <<< FAILURE! - in org.apache.hadoop.hbase.client.TestAdmin1
> [ERROR] org.apache.hadoop.hbase.client.TestAdmin1 Time elapsed: 1.704 s <<< ERROR!
> java.lang.IllegalStateException: A mini-cluster is already running
> at org.apache.hadoop.hbase.client.TestAdmin1.setUpBeforeClass(TestAdmin1.java:97)
> {code}
> So, we timeout after running a test for only 1.3 seconds... but in total it is > 600.
> Then we are on to interesting stuff like minicluster running already. I've seen this in past.
> I could refactor TestAdmin1... let me up the general timeout instead....
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)