Hi All. Just a heads up that I have a PR up (https://github.com/apache/geode/pull/7232) which, if merged, will slightly change the log output from DUnit runs. The PR simply adds a 4 character unique ID to the log line. As in:
[vm0-51ec] [info 2021/12/24 15:43:54.367 UTC <RMI TCP Connection(1)-10.138.0.70>; tid=0x1d] Reinitializing JarDeploymentService with new working directory: null [vm0-47b7] [info 2021/12/24 15:43:54.416 UTC <RMI TCP Connection(1)-10.138.0.70> tid=0x1d] Reinitializing JarDeploymentService with new working directory: null [vm1-47b7] [info 2021/12/24 15:43:54.431 UTC <RMI TCP Connection(1)-10.138.0.70> tid=0x1d] Received method: org.apache.geode.test.dunit.internal.IdentifiableCallable.call with 0 args on object: IdentifiableCallable(0:start locator in vm0) The ID is intended to be unique per test run when tests are run repeatedly. I did this to assist in debugging test output from repeated test runs (StressNewTest) where individual tests’ log lines are simply interleaved making debugging very difficult. The change, unfortunately, does not affect log lines generated from the test VM but only from VMs launched by the ProcessManager. If anyone has ideas how to do that, I’d love to hear them. Well, actually one approach I’ve used is related to this PR (https://github.com/apache/geode/pull/7231) which lets one name ExecutorServiceRule threads. Using this, I can use the ProcessManager.ID to name the executor threads and thus that ID becomes visible when the thread name is logged. Kinda hacky, but it’s still effective. Anyway, this is not a call to review (although you’re welcome to do so) but just a FYI. --Jens
