[MITgcm-devel] After PR #371 (tst_2+2_bug_fix) got merged in

[Jean-Michel Campin]

Hi Martin and Oliver,

There is something unclear regarding the effect of this PR #371:
Since I merged it after mid-night yesterday, only got used in faily tests
last night. And for few restart test where some experiments were failing the 
test, I got a big improvement and many more to pass.

I still have not yet all output back, but the one affected are:
a) 1 more pass on villon (linux_amd64_gfortran.dvlp):
 Y Y Y Y  pass   <- global_ocean.gm_k3d
---
> Y Y Y Y FAIL (4) - global_ocean.gm_k3d
b) 5 more pass on engaging (linux_amd64_open64+mpi.fast):
45c45
< Y Y Y Y  pass   <- global_with_exf
---
> Y Y Y Y FAIL (4) - global_with_exf
56,59c56,59
< Y Y Y Y  pass   <- isomip
< Y Y Y Y  pass   <- isomip.htd
< Y Y Y Y  pass   <- isomip.icefront
< Y Y Y Y  pass   <- isomip.obcs
---
> Y Y Y Y FAIL (4) - isomip
> Y Y Y Y FAIL (4) - isomip.htd
> Y Y Y Y FAIL (4) - isomip.icefront
> Y Y Y Y FAIL (4) - isomip.obcs
c) and the largest changes are from "ollie" (before/after)i, only the "fast" ones:
 46:97  rs_ollie-i_20200922_1                    restart  linux_ia64_ifort_ollie+mpi.fast
 94:97  rs_ollie-i_20200923_1                    restart  linux_ia64_ifort_ollie+mpi.fast
And:
 50:96  rs_ollie-c_20200922_1                    restart  linux_ia64_cray_ollie+mpi.fast
 92:96  rs_ollie-c_20200923_1                    restart  linux_ia64_cray_ollie+mpi.fast

The 1 change in "do_tst_2+2" is unlikely to change anything (because it's just 
for log file and report, and only excecuted once for the first experiment).
So it's something with the 2 changes in "tst_2+2", and may be related to 
disk/system missing an updated file (since it's more common with "fast" than "devel") ?
Not very clear.

Cheers,
Jean-Michel