Mute agent output

[Jonathan Gibbons]

Jorn,

There is currently no way to disable that logging. It would not be good 
to have tests in the test suite that require the logging to be disabled.

One way to handle this is to modify the test so that it runs a wrapper 
class in the agentVM which execs a process in which the main test code 
runs. You can then control how the output to stdout is handled.

This will not require any change to jtreg.

-- Jon

On 2/20/19 4:11 AM, Jorn Vernee wrote:
> Hi,
>
> We are running tests with jtreg that call the native printf function. 
> As a result a lot of agent log output is being printed, e.g.:
>
> [2019-02-20 13:02:24,883] Agent[6]: stdout: hello(str,str,h)
> [2019-02-20 13:02:24,883] Agent[6]: stdout: hello(42,h,h,42)
> [2019-02-20 13:02:24,883] Agent[6]: stdout: hello(h,h,0.0000)
> [2019-02-20 13:02:24,883] Agent[6]: stdout: hello(42,str,42,42)
> [2019-02-20 13:02:24,883] Agent[6]: stdout: hello(h,str,str)
> [2019-02-20 13:02:24,883] Agent[6]: stdout: hello(42,h,str)
> [2019-02-20 13:02:24,883] Agent[6]: stdout: hello(h,h,0.0000,1.2345)
>
> There are a lot of these outputs, and this is filling the entire 
> console buffer, so it ends up erasing the console log from before the 
> test run. Sometimes when I need to look at that I can't because it's 
> erased. I'd like to be able to turn of this logging, since I don't 
> really need to see what's being printed. Is there any way to do this 
> currently?
>
> FWIW, I tried looking into implementing this, but I've not been able 
> to build jtreg with cygwin, since the build-all.sh script is passing 
> cygwin file system (i.e. unix) paths up to Ant, which can not 
> understand those paths. I've tried to work around this by converting 
> the paths to Windows one, but this still ends up blowing up somewhere 
> down the line. Any tips for that as well?
>
> Thanks,
> Jorn