QuarkusMainTest intercepts spurious strings

[andreaTP]

Describe the bug

The QuarkusMainTests are spuriously intercepting output coming from different sources.

Expected behavior

The QuarkusMainTests report back only the output from the specific launched Process.

Actual behavior

No response

How to Reproduce?

I started reducing the error down to a test in this codebase.

In io.quarkus.it.picocli.PicocliTest add the following test:

    @Test
    public void testLogCapturing(QuarkusMainLauncher launcher) {
        org.jboss.logging.Logger.getLogger("test").error("error");
        LaunchResult result = launcher.launch("with-method-sub-command", "hello", "-n", "World!");
        assertThat(result.exitCode()).isZero();
        assertThat(result.getOutput()).isEqualTo("Hello World!");
    }

and the test will fail with an error similar to:

[ERROR] Failures: 
[ERROR]   PicocliTest.testLogCapturing:43 
expected: "Hello World!"
 but was: "2021-12-16 19:28:23,647 ERROR [test] (main) error
Hello World!"
[INFO] 
[ERROR] Tests run: 11, Failures: 1, Errors: 0, Skipped: 0

The expectation is that the test should pass.

Output of uname -a or ver

No response

Output of java -version

No response

GraalVM version (if different from Java)

No response

Quarkus version or git rev

main

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

[quarkus-bot]

/cc @geoand

[DGuhr]

I've spent quite a few hours on this, thanks for the fix Andrea :)

[andreaTP]

You actually found it @DGuhr 👍

[gsmet]

Fixed by #22303.