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

Zhihong Yu commented on HBASE-5831:
-----------------------------------

I captured stack trace twice when the test was running and got similar result:
{code}
"main" prio=5 tid=102801000 nid=0x100601000 waiting on condition [1005fe000]
   java.lang.Thread.State: WAITING (parking)
        at sun.misc.Unsafe.park(Native Method)
        - parking to wait for  <7854b0c00> (a 
java.util.concurrent.FutureTask$Sync)
        at java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
        at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:811)
        at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:969)
        at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1281)
        at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:218)
        at java.util.concurrent.FutureTask.get(FutureTask.java:83)
        at 
org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles.bulkLoadPhase(LoadIncrementalHFiles.java:296)
        at 
org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles.doBulkLoad(LoadIncrementalHFiles.java:248)
        at 
org.apache.hadoop.hbase.mapreduce.TestLoadIncrementalHFilesSplitRecovery.testBulkLoadPhaseFailure(TestLoadIncrementalHFilesSplitRecovery.java:256)
{code}
Maybe disabling testBulkLoadPhaseFailure is enough for Jenkins to get back to 
normal.
                
> hadoopqa builds not completing
> ------------------------------
>
>                 Key: HBASE-5831
>                 URL: https://issues.apache.org/jira/browse/HBASE-5831
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>            Reporter: stack
>            Assignee: stack
>            Priority: Blocker
>         Attachments: 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt, 
> 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt
>
>
> No test failures but build complains it has failed.  trunk build seems to 
> have the same affliction:
> {code}
> Results :
> Tests run: 909, Failures: 0, Errors: 0, Skipped: 9
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Total time: 41:19.273s
> [INFO] Finished at: Wed Apr 18 21:54:31 UTC 2012
> [INFO] Final Memory: 59M/451M
> [INFO] 
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.12-TRUNK-HBASE-2:test 
> (secondPartTestsExecution) on project hbase: Failure or timeout -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> -1 overall.  Here are the results of testing the latest attachment 
>   http://issues.apache.org/jira/secure/attachment/12523250/5811+%281%29.txt
>   against trunk revision .
>     +1 @author.  The patch does not contain any @author tags.
>     +1 tests included.  The patch appears to include 3 new or modified tests.
>     +1 javadoc.  The javadoc tool did not generate any warning messages.
>     +1 javac.  The applied patch does not increase the total number of javac 
> compiler warnings.
>     -1 findbugs.  The patch appears to introduce 6 new Findbugs (version 
> 1.3.9) warnings.
>     +1 release audit.  The applied patch does not increase the total number 
> of release audit warnings.
>      -1 core tests.  The patch failed these unit tests:
> {code}
> Its not apparent that any particular test is not finishing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to