From e17f438b104f7488fc18ff6c180f1eb5f58744a0 Mon Sep 17 00:00:00 2001 From: Scott Mitchell Date: Fri, 22 Dec 2017 09:01:35 -0800 Subject: [PATCH] Test output should include GC details Motivation: Our tests are often asynchronous and have timeouts to avoid hanging indefinitely. However sometimes the timeouts maybe set to low for the CI servers. It would be helpful to confirm if the application was busy with GC and if that was a contributing factor to the test timing out. Modifications: - Unit tests should run with -XX:+PrintGCDetails by default Result: More visibility into GC behavior in unit tests. --- pom.xml | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/pom.xml b/pom.xml index ec953f94bd..aafe329964 100644 --- a/pom.xml +++ b/pom.xml @@ -94,6 +94,12 @@ -Dio.netty.leakDetectionLevel=paranoid -Dio.netty.leakDetection.maxRecords=32 + + noPrintGC + + -D_ + + noUnsafe @@ -180,6 +186,7 @@ -D_ -D_ -D_ + -XX:+PrintGCDetails -D_ @@ -811,7 +818,7 @@ ${logging.config} ${logging.logLevel} - ${argLine.common} ${argLine.alpnAgent} ${argLine.leak} ${argLine.coverage} ${argLine.noUnsafe} ${argLine.java9} ${argLine.javaProperties} + ${argLine.common} ${argLine.printGC} ${argLine.alpnAgent} ${argLine.leak} ${argLine.coverage} ${argLine.noUnsafe} ${argLine.java9} ${argLine.javaProperties} listener