Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
Reviewed
-
Ups the overall test timeout from 10 minutes to 13minutes. 15minutes is the surefire timeout.
Description
TestAdmin1 has 28+ tests. Nightly #336 shows this:
[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)
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....
Attachments
Attachments
Issue Links
- links to
