Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Remove for_testing_allow_non_annual_changes from user_nl_clm

Open
#1,737 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 4 days

@billsacks is already working on this.

Since Oct 23, 2026.

  • #1738 by @billsacks — open

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Stale
Domain
testing

Research direction

Find the outfrq9s_leapday testmod and its user_nl_clm setting; the issue does not name a file path. Read the open pull request #1738 and check whether it already handles this cleanup. Done means the setting is removed without changing meaningful behavior, and relevant tests still pass.

Written by the indexing model from the issue text.

Description

Issue Type

Code Clean-up

Issue Description

The outfrq9s_leapday testmod sets for_testing_allow_non_annual_changes in user_nl_clm. This was added by @kdraeder to allow an ERI test to pass with this testmod.

With the changes in https://github.com/ESCOMP/CTSM/pull/4281, I believe this setting will no longer be needed. It would probably be safe to remove it before that CTSM version is pulled into CAM because I don't think there are currently any ERI tests using the outfrq9s_leapday testmod in any standard test lists - though it might break any additional testing that @kdraeder is doing.

Removing this setting won't change behavior in any meaningful way; this setting just bypassed some error checks that should no longer need to be bypassed. I prefer removing this setting so that we're not unnecessarily bypassing error checks.

Will this change answers?

No

Will you be implementing this yourself?

Yes

Dominant language
No language data
Stars
93
Forks
186
Avg merge
4d 21h
Merged PRs (30d)
18

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ESCOMP/CAM

All issues in ESCOMP/CAM

Similar issues

More Testing & QA issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.