build output/logging buffering?

[Fredrik Öhrström]

stderr and stdout are always independent and stderr writing is usually
visible earlier
than stdout writing because it is not buffered. The timing of stderr and
stdout
is probably drifting apart even more because of the logger script.

You can patch the spec file to get rid of the logger and see if it
affects your ordering. Set BUILD_LOG_WRAPPER to the empty string.

//Fredrik

Den lördagen den 30:e juni 2012 skrev Kelly O'Hair:

> That logger.sh script is doing some strange buffering to fd 3 somehow.
> I'd never see that used before.
>
>
> http://hg.openjdk.java.net/build-infra/jdk8/file/ccfffd988af6/common/bin/logger.sh
>
>
> -kto
>
> On Jun 29, 2012, at 2:57 PM, Erik Joelsson wrote:
>
> > This problem was new to me. It seems strange that stderr and stdout
> would behave differently. Both are piped through a separate instance of
> 'tee' to preserver the separation on the console, but to get both into the
> logfile.
> >
> > /Erik
> >
> > On 2012-06-28 20:16, David Holmes wrote:
> >> I see that a build will create a build.log by default. I also see I can
> set VERBOSE= to get back to the older more verbose style of output (eg full
> compilation commands etc).
> >>
> >> But it seems that due to the logging there is some buffering taking
> place that prevents me from seeing the most recent build output while it is
> running. I just had a problem where due to a mistyped variable I did a "cd
> " and then starting trawling my entire home directory, but I couldn't see
> this in the build output, ie no "cd " was visible, presumably because the
> output was being buffered.
> >>
> >> What I did see, which gave me the hint were a bunch of warnings that
> presumably went to stderr, not stdout and do did not get buffered.
> >>
> >> David
> >
>
>