[
https://issues.apache.org/jira/browse/HBASE-11911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14131860#comment-14131860
]
stack commented on HBASE-11911:
-------------------------------
I see this in the raw console output. It showed up in previous run IIRC. Let
me run this patch local. I want to see if we run all tests. I don't see why
not. Nor do I see how the failures are related to this change.
{code}
....
Running org.apache.hadoop.hbase.regionserver.TestFlushRegionEntry
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.694 sec - in
org.apache.hadoop.hbase.regionserver.TestFlushRegionEntry
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/dev-support/test-patch.sh:
line 685: 3689 Killed $MVN clean test -P runAllTests
-D${PROJECT_NAME}PatchProcess
Suspicious java process found - waiting 30s to see if there are just slow to
stop
There are 1 zombie tests, they should have been killed by surefire but survived
************ BEGIN zombies jstack extract
2014-09-12 05:48:18
Full thread dump Java HotSpot(TM) 64-Bit Server VM (24.51-b03 mixed mode):
"Attach Listener" daemon prio=10 tid=0x00007f1138001000 nid=0x556b waiting on
condition [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
"process reaper" daemon prio=10 tid=0x00007f11906cc800 nid=0x54f2 waiting on
condition [0x00007f116e2d6000]
java.lang.Thread.State: TIMED_WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x00000007e4400578> (a
java.util.concurrent.SynchronousQueue$TransferStack)
at
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226)
at
java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(SynchronousQueue.java:460)
at
java.util.concurrent.SynchronousQueue$TransferStack.transfer(SynchronousQueue.java:359)
at java.util.concurrent.SynchronousQueue.poll(SynchronousQueue.java:942)
at
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
....
{code}
> Break up tests into more fine grained categories
> ------------------------------------------------
>
> Key: HBASE-11911
> URL: https://issues.apache.org/jira/browse/HBASE-11911
> Project: HBase
> Issue Type: Sub-task
> Reporter: Alex Newman
> Assignee: Alex Newman
> Attachments: HBASE-11911-preview.patch, HBASE-11911-v0.patch,
> HBASE-11911-v1.patch, HBASE-11911-v2.patch, HBASE-11911-v3.patch,
> HBASE-11911-v3.patch, HBASE-11911-v4.patch, HBASE-11911-v4.patch,
> HBASE-11911-v5.patch
>
>
> Wouldn't it be nice to run all of the client tests (client and the ones in
> hbase-server) in a single command like.
> mvn test -PrunClientTests
> how about all of the small tests not having to do with mapReduce
> mvn test -PrunSmallTests,!runMapReduceTests
> how about breaking up the build into small pieces so it can be run on travis
> or circle-ci. If that's what you are into, +1 this patch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
