debugging output

Aleksey Shipilev aleksey.shipilev at oracle.com
Wed Oct 3 01:31:50 PDT 2012


Can we please move forward with this? I can throw together a patch if
others are overblown with J1 at this point.

-Aleksey.

On 09/27/2012 10:23 PM, Aleksey Shipilev wrote:
> Thanks!
> 
> On 09/27/2012 08:23 PM, Mike Duigou wrote:
>> I'll switch the System.(err|out).print statements to j.u.Logger with level warning. This will allow them to be silenced using standard measures. 
>>
>> Mike
>>
>> On Sep 27 2012, at 04:11 , Aleksey Shipilev wrote:
>>
>>> On 09/26/2012 01:34 AM, Aleksey Shipilev wrote:
>>>> On 09/25/2012 08:29 PM, Brian Goetz wrote:
>>>>> We're currently at zero on the latter and I want to stay that way :)
>>>>
>>>> I'm actually fine on the whole tripwire thing. Let it just be less
>>>> annoying (e.g. our nightly tests produced 50+ Mb of logs per run filled
>>>> with these outputs; that pretty much blowing up the entire continent
>>>> triggered by single booby-trap), hence the printOnce suggestion.
>>>
>>> So, nothing on this? Once again, here the proposed patch:
>>> http://shipilev.net/pub/jdk/lambda/printOnce.patch
>>>
>>> -Aleksey.
>>>
>>>
>>
> 
> 



More information about the lambda-dev mailing list