From 15339a25ecdfdc4e790044eb22f0fe172486cca6 Mon Sep 17 00:00:00 2001
From: Kevin Turner <83819+keturn@users.noreply.github.com>
Date: Fri, 8 May 2020 13:04:20 -0700
Subject: [PATCH] upgrade game log output from TRACE to INFO

This does is a spec change, but the best way to avoid this "test failure won't show us TRACE output unless we use the @CollectLogs decorator" is to not rely on TRACE output.

Especially since we want game output more visible anyway, for troubleshooting on launch failure.
---
 .../java/org/terasology/launcher/game/TestRunGameTask.java | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/src/test/java/org/terasology/launcher/game/TestRunGameTask.java b/src/test/java/org/terasology/launcher/game/TestRunGameTask.java
index c763f5f41..92fdd13a3 100644
--- a/src/test/java/org/terasology/launcher/game/TestRunGameTask.java
+++ b/src/test/java/org/terasology/launcher/game/TestRunGameTask.java
@@ -104,9 +104,10 @@ public void testGameOutput() throws InterruptedException, RunGameTask.GameExitEr
 
         var hasGameOutputFormat = LogMatchers.hasFormatWithPattern("^Game output.*");
 
-        LogAssert detailedExpectation = TestLoggers.sys().expect(RunGameTask.class.getName(), Level.TRACE,
-                                                                 allOf(hasGameOutputFormat, LogMatchers.hasArguments(gameOutputLines[0])),
-                                                                 allOf(hasGameOutputFormat, LogMatchers.hasArguments(gameOutputLines[1]))
+        LogAssert detailedExpectation = TestLoggers.sys().expect(
+                RunGameTask.class.getName(), Level.INFO,
+                allOf(hasGameOutputFormat, LogMatchers.hasArguments(gameOutputLines[0])),
+                allOf(hasGameOutputFormat, LogMatchers.hasArguments(gameOutputLines[1]))
         );
 
         gameTask.monitorProcess(gameProcess);