Changes between Version 21 and Version 22 of addnewNR


Ignore:
Timestamp:
01/30/26 12:48:40 (3 weeks ago)
Author:
Mathieu Morlighem
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • addnewNR

    v21 v22  
    33ISSM relies on regression tests to check that no bug is introduced during code development. All the tests are located in `$ISSM_DIR/test/test/NightlyRun` and all the tests whose number are less than 1000 are run after each change pushed to the svn repository (through jenkins: https://ross.ics.uci.edu/jenkins/). See [wiki:jenkins] for more information.
    44
    5 If a new capability is being added to ISSM, it is *critical* that a new test is created.
     5If a new capability is being added to ISSM, it is **absolutely critical** that a new test is created.
    66
    77These nightly runs are not meant to be realistic. They rely on very coarse meshes. We only want to check that the numerics has not changed, the results are obviously meaningless. Each test should take less than 10 seconds to run (ideally 1 second).
     
    9393In the case of a brand new test
    9494{{{
    95 svn add test/NightlyRun/testXXX.m test/NightlyRun/testXXX.py test/Archives/ArchiveXXX.arch
     95git add test/NightlyRun/testXXX.m test/NightlyRun/testXXX.py test/Archives/ArchiveXXX.arch
    9696}}}
    9797then,
    9898{{{
    99 svn commit –m "NEW: Added test to check ...”`
     99git commit –m "NEW: Added test to check ..."
     100git push
    100101}}}
    101102with an appropriate message. Otherwise you can simply update the archive and commit the changes.