My guess is that there is a background thread that throws a CancelException which is caught and logged AFTER the DistributedSystem disconnect. Any logging after that goes to stdout logging instead of the server/locator log file.
Otherwise, it might be a System.out or throwable.printStackTrace call somewhere in the code. On Thu, Jun 25, 2020 at 11:35 PM Alberto Gomez <alberto.go...@est.tech> wrote: > Hi Kirk, > > I build on Ubuntu 18.02 and I occasionally see the partial stack traces > you mentioned on geode-wan:tests you mentioned. So it is not just a Windows > thing. > > Never figured out what they provoked them and neither how to get them > consistently. > > BR, > > Alberto > > ________________________________ > From: Kirk Lund <kl...@apache.org> > Sent: Thursday, June 25, 2020 11:53 PM > To: dev@geode.apache.org <dev@geode.apache.org> > Subject: Successful build on windows > > In case anyone is interested in the developer experience building with unit > tests on windows: > > It succeeds (after a couple tries) but something in geode-wan:test spits > out a partial stack trace. Since all the tests passed, I don't really see a > way to find out which test generated it. > > C:\Users\kirkl\dev\geode>gradlew.bat build > > > > *> Task :geode-wan:test at > > org.apache.geode.internal.cache.wan.parallel.ParallelGatewaySenderQueue$BatchRemovalThread.checkCancelled(ParallelGatewaySenderQueue.java:1780) > at > > org.apache.geode.internal.cache.wan.parallel.ParallelGatewaySenderQueue$BatchRemovalThread.run(ParallelGatewaySenderQueue.java:1879)* > > > Task :combineReports > All test reports at C:\Users\kirkl\dev\geode\build/reports/combined > > Deprecated Gradle features were used in this build, making it incompatible > with Gradle 6.0. > Use '--warning-mode all' to show the individual deprecation warnings. > See > > https://docs.gradle.org/5.4/userguide/command_line_interface.html#sec:command_line_warnings > > BUILD SUCCESSFUL in 3m 52s > 532 actionable tasks: 97 executed, 435 up-to-date >
