There is a ticket open for a hang in the other test method in that same
class.
On 1/23/19 10:04 AM, Kirk Lund wrote:
Looks like there's a Test worker thread that keeps running and changing.
Maybe the dunit test is pushing the dunit job over its time limit:
"Test worker" #27 prio=5 os_prio=0 cp
Dan, 5676 is for the other test in the same class. I'm working on that
other test as part of fixing GEODE-6309.
On 1/23/19 10:43 AM, Dan Smith wrote:
Thanks Kirk - this is GEODE-5676. I'm glad the callstacks are finally
working again, that should help us track this down! I'll update that ticke
Thanks Kirk - this is GEODE-5676. I'm glad the callstacks are finally
working again, that should help us track this down! I'll update that ticket
with anything I can figure out from this failure.
-Dan
On Wed, Jan 23, 2019 at 10:05 AM Kirk Lund wrote:
> Looks like there's a Test worker thread th
Looks like there's a Test worker thread that keeps running and changing.
Maybe the dunit test is pushing the dunit job over its time limit:
"Test worker" #27 prio=5 os_prio=0 cpu=1332.79ms elapsed=4871.91s
tid=0x7f67c4a78800 nid=0x1c runnable [0x7f675fbf3000]
java.lang.Thread.State: RU
