logger script

[Kelly O'Hair]

What I noticed, and this was highly unscientific, was that Linux and Solaris builds with JPRT seemed
to be about 5-10% slower. If that is true, do we want that overhead? Or what kind of overhead is acceptable?
So I think it is reliable on Solaris and Linux, just wondering how much it is really costing us.
Not sure on the Mac, but the Mac has had some pretty strange behaviors when loaded down, but I cannot
point at the logger script with regards to that.

Windows is just the sh1ts no matter what. ;^(

-kto

On Sep 6, 2012, at 12:49 AM, Erik Joelsson wrote:

> Have you seen problems on any other platforms than windows? If it's not working reliably, it will need to be disabled, but preferably only on the unreliable platform.
> 
> /Erik
> 
> On 2012-09-06 06:14, Kelly O'Hair wrote:
>> The logger mechanism (common/bin/logger.sh) is clever and everything, but it appears to be
>> costing us build time (10% on some platforms) and more importantly build stability on windows.
>> Fancy shell exec logic doesn't seem to be as reliable on windows and just slows it down badly. :^(
>> 
>> My tendency is to have it default to being off (e.g. have BUILD_LOG_WRAPPER be empty)
>> unless we can determine we have a developer doing a build.
>> Or alternatively we need some kind of 'batch build' setting for build systems.
>> 
>> I'm open to ideas here.
>> 
>> -kto
>>