[MITgcm-devel] testreport - ed can you address this?

[Andrea Molod]

hi there,

i have a comment and a suggestion about testreport.
at present, when a test (on faulks) fails the monitor comparison
the output is lost (except for the adjoint tests). this means
that the test has to be re-run in order to see what went wrong.
i understand that keeping the output.txt files for all tests
on the web 'forever' puts a silly strain on disk space. so -
can we keep the 'last' output.txt from a run that failed the
monitor comparison (either because it croaked or because there
is no monitor output) on faulks in /scratch and NOT include
it in the tar file that gets made to put stuff on the web?
i say all this for faulks because i am not sure how stuff
works for remote machines (ie, columbia), and because faulks
is the machine that is used for the benchmark (so i at least
am more likely to want to track down why a test there fails....).

i guess that my main question is whether others would like to
see this stuff saved, and how much of a pain it would be to
change testreport and the run scripts that invoke it.....

thanks ed,

andrea

----------------------------------------------------------------
Andrea M. Molod, PhD.
Department of Earth, Atmospheric & Planetary Sciences
MIT
Tel: (617) 253-5458, Email: amolod at mit.edu
WWW:http://paoc.mit.edu/paoc/people/person.asp?position=Postdoc&who=molod
----------------------------------------------------------------