Add unit-testers for FORTRAN code in CMEPS
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- fortran
- Domain
- testing
Research direction
Read issue #429 and the CTSM pull request that introduced the FORTRAN code and tester. Clarify the intended CMEPS/CTSM ownership and build path with maintainers. Done would be an agreed, reproducible unit-test arrangement for CMEPS, including how CTSM builds and runs it.
Written by the indexing model from the issue text.
Description
In #429 I added new code and a unit-tester for it under the CTSM PR that uses it. I'm wondering if unit-testers is something that should be added to CMEPS? Initially maybe the way to go would be to have the unit-tester in CMEPS, but still use the CTSM infrastructure to build and run it?
@billsacks thoughts on this?
- Dominant language
- Fortran
- Stars
- 36
- Forks
- 107
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ESCOMP/CMEPS
-
Latent heat bug in COARE atm/ocn flux routine for CESMMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
enhancement question
Difficulty 2/5 1-3 hours Newbie friendliness 40/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
[BUG] Container scenario crashes without expected_recovery_time, kube DNS example uses retry_waitOpenneeds-triage
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
krkn-chaos/krkn#1627 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
spring-projects/spring-grpc#442 ·
-
api: vertex-ai
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/python-aiplatform#7208 · 1 comment ·
Maintainers usually reply within 2 days
-
ready
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
kubeflow/pipelines#14784 · 1 comment ·
Maintainers usually reply within 2 days