#1655 closed Bug (fixed)
SETTE test fails if your installation path contains "SETTE" keyword
| Reported by: | mcastril | Owned by: | nemo |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | OCE | Version: | v3.6 |
| Severity: | Keywords: | OPA v3.6 | |
| Cc: |
Description
Maybe is not a common issue but if you have your test versions in a path containing "SETTE", the script chops the path string and SETTE doesn't run.
For example:
/filesystem/NEMO/TESTS/SETTE/nemo_v3.6/NEMOGCM
It will think that NEMO_DIR is /filesystem/NEMO/TESTS
Commit History (2)
| Changeset | Author | Time | ChangeLog |
|---|---|---|---|
| 6460 | lovato | 2016-04-08T18:00:29+02:00 | Move runoff fields time swap in sbcmod (#1703) and change SETTE path definition of MAIN_DIR (#1655) |
| 6459 | lovato | 2016-04-08T18:00:11+02:00 | Move runoff fields time swap in sbcmod (#1703) and change SETTE path definition of MAIN_DIR (#1655) |
Change History (3)
comment:1 Changed 9 years ago by timgraham
comment:2 Changed 8 years ago by lovato
- Resolution set to fixed
- Status changed from new to closed
comment:3 Changed 2 years ago by nemo
- Keywords OPA v3.6 added
Note: See
TracTickets for help on using
tickets.
It is minor but still quite annoying at times.
I think it can be fixed quite easily by replacing
MAIN_DIR=${SETTE_DIR%/SETTE}with
in the sette.sh script.