Hi folks,
Running this test with fastdebug binaries results in a few warning
messages getting lumped into the commandOutput. I've decided to filter
these test wide.
https://bugs.openjdk.java.net/browse/JDK-6703075
http://cr.openjdk.java.net/~robm/6703075/webrev.01/
-Rob
On 19/11/2013 16:46, Rob McKenna wrote:
Hi folks,
Running this test with fastdebug binaries results in a few warning
messages getting lumped into the commandOutput. I've decided to filter
these test wide.
https://bugs.openjdk.java.net/browse/JDK-6703075
Great, thanks Martin. I totally overlooked that flag while hunting
around globals.hpp. I've added your contribution here:
http://cr.openjdk.java.net/~robm/6703075/webrev.02/
-Rob
On 19/11/13 19:58, Martin Buchholz wrote:
I propose a fix like the diff below, that asks the VM to separate
On 19/11/2013 19:58, Martin Buchholz wrote:
I propose a fix like the diff below, that asks the VM to separate
regular output and JVM output into stdout and stderr, so that we can
do matching on each independently, and so that we can rely on stdout
not being corrupted by JVM output.
Good, it's
