> The parent process or the worker child? The parent. The reason here was to avoid spawning a background thread on the child to avoid any interference with existing tests. So the parent tracks events that tell where the child is going (entering or leaving a suite/ test) and is from this deducing where a child may be. The <unknown> status means the child is not executing any suite; it used to be the case that OOM-ed code would hang forever on System.exit, for example...
> Can you see from the messages *where* it might hang? Not really, not if it's a JVM issue. > Interestingly another one is now hanging with the following message: > > [junit4:junit4] HEARTBEAT J0 PID(11405@serv1): 2013-03-04T13:16:16, stalled > for 7086s at: UIMABaseAnalyzerTest.baseUIMAAnalyzerIntegrationTest If this one is not responsive to regular stack trace probing then it's definitely a JVM freeze somewhere. D. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
