Changes between Version 10 and Version 11 of Rose/Rose Stem FAQ


Ignore:
Timestamp:
Oct 30, 2020 11:29:46 AM (4 weeks ago)
Author:
Susan Rennie
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Rose/Rose Stem FAQ

    v10 v11  
    9292
    93931. Create a ticket and cc at least one code owner, plus appropriate ITO (if you aren't one).
    94 2. Create  a branch off the trunk.
    95 3. Compile and run the stem tests to see which ones fail rose-ana.
     942. Create  a branch off the trunk. (`fcm bc -k <ticket_number> <branch name, e.g. update_kgo> <URL to trunk, e.g. https://code.metoffice.gov.uk/svn/ops/main/trunk or fcm:ops.x/trunk>`)
     953. Compile and run the stem tests to see which ones fail rose-ana. (`rose stem --task=bomall` for OPS or `rose stem --task=R_ALL` for VAR/SURF)
    96964. At this point you might want to check why the tests are failing.
    9797 - Most changes that affect the results are listed on the !LoseBitComparison page, which is linked on the front wiki page of the relevant code component. From here, you can see which tickets affected which tests.
     
    103103 - Create a new directory for the controls, which for example is named "control-t<ticket_number>", either the ticket number which altered the code, or your ticket to update the controls. If several tickets have contributed to changes, you should instead name the new controls for the revision number of the trunk for which your controls are valid, i.e. "control-r<revision_number>.
    104104 - Into this directory copy the log and work directories, i.e. {{{cp $CYLC_SUITE_DIR/log <your_control_dir>; cp $CYLC_SUITE_DIR/work <your_control_dir>}}}
    105 6. Modify the <your_branch>/rose-stem/site/nci/<component>/suite-controls.rc to point to your control dir for the relevant tasks. There is a script to do this automatically, which is useful if many controls are being updated. It is held in one of the repositories.
     1056. Modify the <your_branch>/rose-stem/site/nci/<component>/suite-controls.rc to point to your control dir for the relevant tasks. There is a script to do this automatically, which is useful if many controls are being updated. It is held in one of the repositories (var_trunk/rose-stem/bin/update_controls).
    1061067. Rerun the stem tests and check that no rose-anas fail.
    1071078. If necessary, get an ITO to copy the new controls to the correct directory, then repeat the above two steps, with the correct path.
    108 9. Commit your changes to the repository
     1089. Commit your changes to the repository (`fcm ci` or `fcm commit`)
    10910910. Update your ticket with changeset info and anything else
    11011011. Submit your ticket for review and assign to a code owner.