GitList

Browse code

change the order of the print/flush

It seems that we get a different behavior whether stdout is closed
in the parent process or not when it comes to buffering. If it's
closed we don't get the last line flushed out to the file, if it's
not closed we do. This was seen in the trove pg fail.

A complete shot in the dark, but I'd like to see if this is fixed
with being explicit with printing to the log before stdout.

Change-Id: Ie37299dbc88d549d34d85731e571a5b7ef181311

Sean Dague authored on 2014/03/16 02:50:36
Showing 1 changed files

stack.sh index 09e9eec..7fa4d37 100755

stack.sh

History View file @ 7afffa6

@@ -538,10 +538,10 @@ if [[ -n "$LOGFILE" ]]; then
                                          cmd | getline now
                                          close("date +\"%Y-%m-%d %H:%M:%S.%3N | \"")
                                          sub(/^/, now)
                     -                    print
                                          print > logfile
                     -                    fflush("")
                                          fflush(logfile)
                     +                    print
                     +                    fflush("")
                                      }' ) 2>&1
                              # Set up a second fd for output
                              exec 6> >( tee "${SUMFILE}" )