280128 - Tinderbox client scripts should output to a new log file for each build

Status: RESOLVED WONTFIX

(Webtools Graveyard :: Tinderbox, defect)

Description

[Chase Phillips]

The Tinderbox client scripts currently output to one log file and then move that
log file to <log>.last after the build is complete.  If I am reading this file
during the build (specifically) while it attempts to move the file or add on to
it, Bad Things Happen.

Work around this problem by creating a new log file per build.  Create a logs
directory if it doesn't exist, create a directory named based on the timestamp,
put the real log file there.  Create a symlink from the log file to the old log
location.

Comment 1

[timeless]

you really plan to create a symlink on windows? :)

Comment 2

[Chase Phillips]

If I couldn't the lack of uniformity would make this a non-starter.

Cygwin has ln which creates a Windows shortcut on the backend.  Our build
machines are set up by creating a directory for a tree and then a set of
symlinks to the Tn client scripts in a CVS checkout of tools/tinderbox/ that all
trees on that system use.

Most of our machines are set up like this already.  The ones that aren't are
being transitioned to it.

Comment 3

[Chase Phillips]

Mass reassign of open bugs for [e-mail] to [e-mail].