Testing pipeline (gitlab)

Notes on gitlab pipeline

• The list of tests to run is defined by the "stats" files recorded in the regression repository (Gaea-stats hosted on gitlal.gfdl.noaa.gov)
• When the queue wait time is minimal, the testing on c4 takes approximately 45 minutes end-to-end.

1. Setup stage
   • Recursive clone of regressions repository dev/gfdl
   • Merge of MOM6 pull request with dev/gfdl
2. Build stage
   • Compiles a symmetric and non-symmetric executables for each configuration:
     • ocean-only
     • ice-ocean (SIS2)
     • land-ice-ocean
     • fully coupled
   • For each of the above using each of the following compiler vendor/mode combinations:
     • Gnu debug
     • Gnu repro
     • Intel repro
     • PGI repro
     • Gnu static-memory repro
3. Run stage Note: The run stage does not generate an error code unless the job fails to submit.
   • For all experiment configurations:
     • Run with symmetric executable for each of Gnu, Intel and PGI repro.
     • Run with non-symmetric executable for each of Gnu, Intel and PGI repro with an alternative layout.
   • Run with static-memory Gnu repro
   • Run restart tests with symmetric Gnu repro executable.
4. Test stage
   • Check that non-symmetric tests ran and reproduce regression results.
   • Check that symmetric tests ran and reproduce non-symmetric output.
   • Check that static tests ran and reproduce regression results.
5. Cleanup stage
   • Used to cleanup tar files used for caching executables and output between stages.