Commit 0b116a1a authored by Andy Wilkinson's avatar Andy Wilkinson

Increase the level of JUL logging calls in the tests to try to fix CI

The CI build is failing, but, for some reason, the same tests are
working fine on developer machines. This commit increases the level
at which the logging calls are being made to severe in the hope that
some CI-specific configuration is filtering out the calls when
they're at info level.
parent 6c66ff78
......@@ -95,7 +95,7 @@ public class Log4JLoggingSystemTests {
this.loggingSystem.initialize();
java.util.logging.Logger julLogger = java.util.logging.Logger
.getLogger(getClass().getName());
julLogger.info("Hello world");
julLogger.severe("Hello world");
String output = this.output.toString().trim();
assertTrue("Wrong output:\n" + output, output.contains("Hello world"));
}
......
......@@ -96,7 +96,7 @@ public class Log4J2LoggingSystemTests {
this.loggingSystem.initialize();
java.util.logging.Logger julLogger = java.util.logging.Logger
.getLogger(getClass().getName());
julLogger.info("Hello world");
julLogger.severe("Hello world");
String output = this.output.toString().trim();
assertTrue("Wrong output:\n" + output, output.contains("Hello world"));
}
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment