Enrico If I get the approach correctly then all my junit4 tests should have timeout specified (either via @Test or via @Rule) then only I can use the listener. But the problem is we are having more than 2000 tests and specifying a timeout in each of the tests/classes is cumbersome.
Correct me if I have misunderstood anything. On Fri, Oct 4, 2019 at 3:18 PM Debraj Manna <subharaj.ma...@gmail.com> wrote: > Yeah sure ... thanks. > > On Thu, Oct 3, 2019 at 7:50 PM Tibor Digana <tibordig...@apache.org> > wrote: > >> Hi Debraj, >> >> There is nice technical idea from Enrico. >> If you apply it and you are convinced that it would work properly for all >> the Java community, feel free to show it and we can discuss it on how we >> would adopt your solution in Surefire project. >> >> Cheers >> Tibor17 >> >> On Thu, Oct 3, 2019 at 2:49 PM Debraj Manna <subharaj.ma...@gmail.com> >> wrote: >> >> > Sometimes I have maven surefire tests that get hung, due to either >> races or >> > deadlocks. >> > >> > When this happens I have to discover what slave is being used, and then >> I >> > have to log on that slave, sudo to jenkins account and execute either >> > jstack or kill -3 >> > >> > I am looking for a simple solution like doing jstack / kill -3 when >> someone >> > presses abort button on the jenkins. >> > >> > Can someone suggest how can I automate this or some better way of >> handling >> > this? >> > >> >
