[MITgcm-devel] 2 steps testreport run

[Jean-Michel Campin]

Hi Amato,

I added an option to testreport to just do the run part.
This could help in setting an MPI testreport test 
when compiler (and make) is only available on the front node,
while the MPI run needs to be on compute nodes (e.g. through
a batch system). In this case, I would try a 2 steps procedure:

step.1, on front node:
 testreport -mpi -norun -a NONE -optfile my_optfile (...)
(note that the address "NONE" force testreport to build 
 the mpack utility but does not send any email)

step.2, in a batch job, on compute nodes:
 testreport -mpi -runonly (-a my_address) -optfile my_optfile \
  -command my_mpirun_command (...)

If you don't have the possibility to send email from compute nodes,
you can try to collect & send the output dir when the batch-job is finished,
and send it separatly from the front node (there is an example of this 
 in MITgcm/tools/example_scripts/ACESgrid/aces_test_all)

I think all bits have been tested separately, but never for real 
on a platform with no compiler on compute nodes. So, if you find
something not working or strange, just let us know.

Thanks,
Jean-Michel

PS: cc to devel list so that we keep a reccord.