----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/45142/#review124838 -----------------------------------------------------------
So we will keep the test and add some comments? - Jianxia Chen On March 22, 2016, 1:10 a.m., Jianxia Chen wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/45142/ > ----------------------------------------------------------- > > (Updated March 22, 2016, 1:10 a.m.) > > > Review request for geode, Bruce Schuchardt, Darrel Schneider, Hitesh > Khamesra, and Udo Kohlmeyer. > > > Repository: geode > > > Description > ------- > > The thread dump does not see any suspicious thread: > Two gradle threads; > Three JVM threads: Signal Dispatcher, Finalizer and Reference Handler; > and two test threads: main and Test worker which prints the stack trace. > There is no thread leak as the dunit test is supposed to catch. > > Remove the test. Since different number of threads at the beginning and at > the end of the test does not always mean a thread leak. There could be thread > spawned by gradle or JVM at unpredictable time. > > > Diffs > ----- > > geode-core/src/test/java/com/gemstone/gemfire/cache/Bug42039JUnitTest.java > dc023a9 > > Diff: https://reviews.apache.org/r/45142/diff/ > > > Testing > ------- > > > Thanks, > > Jianxia Chen > >
