Seeing the same with the java11-experimentation build here:

# Created on 2019-03-01T18:01:43.414
Corrupted STDOUT by directly writing to native stream in forked JVM 1.
Stream 'java.lang.OutOfMemoryError: Java heap space'.
java.lang.IllegalArgumentException: Stream stdin corrupted. Expected comma
after third character in command 'java.lang.OutOfMemoryError: Java heap
space'.
        at
org.apache.maven.plugin.surefire.booterclient.output.ForkClient$OperationalData.<init>(ForkClient.java:511)
        at
org.apache.maven.plugin.surefire.booterclient.output.ForkClient.processLine(ForkClient.java:209)
        at
org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:176)
        at
org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:88)
        at java.lang.Thread.run(Thread.java:748)


# Created on 2019-03-01T18:01:43.414
Corrupted STDOUT by directly writing to native stream in forked JVM 1.
Stream 'Dumping heap to java_pid9348.hprof ...'.
java.lang.IllegalArgumentException: Stream stdin corrupted. Expected comma
after third character in command 'Dumping heap to java_pid9348.hprof ...'.
        at
org.apache.maven.plugin.surefire.booterclient.output.ForkClient$OperationalData.<init>(ForkClient.java:511)
        at
org.apache.maven.plugin.surefire.booterclient.output.ForkClient.processLine(ForkClient.java:209)
        at
org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:176)
        at
org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:88)
        at java.lang.Thread.run(Thread.java:748)


# Created on 2019-03-01T18:02:39.417
Corrupted STDOUT by directly writing to native stream in forked JVM 1.
Stream 'Heap dump file created [3085481793 bytes in 56.000 secs]'.
java.lang.IllegalArgumentException: Stream stdin corrupted. Expected comma
after third character in command 'Heap dump file created [3085481793 bytes
in 56.000 secs]'.
        at
org.apache.maven.plugin.surefire.booterclient.output.ForkClient$OperationalData.<init>(ForkClient.java:511)
        at
org.apache.maven.plugin.surefire.booterclient.output.ForkClient.processLine(ForkClient.java:209)
        at
org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:176)
        at
org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:88)
        at java.lang.Thread.run(Thread.java:748)

If we're creating heap dumps, we ought to kill that build, and try and
figure out what's going on.

Thoughts?

Jon

On Fri, Mar 1, 2019 at 9:13 PM j4fm <[email protected]> wrote:

> Getting this WARNING on :cdi-tomee on buildbot which is taking forever...
>
> # Created on 2019-03-01T20:48:20.010
> Corrupted STDOUT by directly writing to native stream in forked JVM 1.
> Stream 'java.lang.OutOfMemoryError: Java heap space'.
> java.lang.IllegalArgumentException: Stream stdin corrupted. Expected comma
> after third character in command 'java.lang.OutOfMemoryError: Java heap
> space'.
>         at
>
> org.apache.maven.plugin.surefire.booterclient.output.ForkClient$OperationalData.<init>(ForkClient.java:511)
>         at
>
> org.apache.maven.plugin.surefire.booterclient.output.ForkClient.processLine(ForkClient.java:209)
>         at
>
> org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:176)
>         at
>
> org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:88)
>         at java.lang.Thread.run(Thread.java:745)
>
>
> # Created on 2019-03-01T20:48:20.027
> Corrupted STDOUT by directly writing to native stream in forked JVM 1.
> Stream 'Dumping heap to java_pid187.hprof ...'.
> java.lang.IllegalArgumentException: Stream stdin corrupted. Expected comma
> after third character in command 'Dumping heap to java_pid187.hprof ...'.
>         at
>
> org.apache.maven.plugin.surefire.booterclient.output.ForkClient$OperationalData.<init>(ForkClient.java:511)
>         at
>
> org.apache.maven.plugin.surefire.booterclient.output.ForkClient.processLine(ForkClient.java:209)
>         at
>
> org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:176)
>         at
>
> org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:88)
>         at java.lang.Thread.run(Thread.java:745)
>
>
> # Created on 2019-03-01T20:49:04.600
> Corrupted STDOUT by directly writing to native stream in forked JVM 1.
> Stream 'Heap dump file created [3106753056 bytes in 44.621 secs]'.
> java.lang.IllegalArgumentException: Stream stdin corrupted. Expected comma
> after third character in command 'Heap dump file created [3106753056 bytes
> in 44.621 secs]'.
>         at
>
> org.apache.maven.plugin.surefire.booterclient.output.ForkClient$OperationalData.<init>(ForkClient.java:511)
>         at
>
> org.apache.maven.plugin.surefire.booterclient.output.ForkClient.processLine(ForkClient.java:209)
>         at
>
> org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:176)
>         at
>
> org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:88)
>         at java.lang.Thread.run(Thread.java:745)
>
>
>
> --
> Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>

Reply via email to