Print luatest logs to stdout when unified log is disabled

If unified logging is enabled, logs written by the runner are written
both to its own log file and to the unified log file. This is consistent
with how logs written by test processes are handled. However, if unified
logging is disabled, then runner logs are written only to its log file
while test process logs are also written to stdout and captured if
capturing is enabled. Let's write runner logs to stdout in this case as
well because they can be useful for debugging.

No changelog because the feature was added by commit f8a1c10
("Add logging to unified file"), which hasn't been released yet.

Author: locker

luatest/runner.lua

@@ -72,16 +72,17 @@ function Runner.run(args, options)
             local fh = fio.open(options.log_file, {'O_CREAT', 'O_WRONLY', 'O_TRUNC'},
                                 tonumber('640', 8))
             rawset(_G, 'log_file', {fh = fh})
+        end
 
-            local output_beautifier = OutputBeautifier:new({prefix = log_prefix})
-            output_beautifier:enable()
+        local output_beautifier = OutputBeautifier:new({prefix = log_prefix})
+        output_beautifier:enable()
+
+        -- `tee` copy logs to file and also to standard output, but we need
+        -- process all captured data through the OutputBeatifier object.
+        -- So we redirect stdout to the pipe created by OutputBeautifier.
+        log_cfg = string.format("| tee %s > /dev/fd/%d",
+                                log_cfg, output_beautifier.pipes.stdout[1])
 
-            -- `tee` copy logs to file and also to standard output, but we need
-            -- process all captured data through the OutputBeatifier object.
-            -- So we redirect stdout to the pipe created by OutputBeautifier.
-            log_cfg = string.format("| tee %s > /dev/fd/%d",
-                                    log_cfg, output_beautifier.pipes.stdout[1])
-        end
         -- Logging cannot be initialized without configuring the `box` engine
         -- on a version less than 2.5.1 (see more details at [1]). Otherwise,
         -- this causes the `attempt to call field 'cfg' (a nil value)` error,