build_status blocks case rebuild
Maintainers usually reply within 1 day
@ekluzek is already working on this.
Since Oct 7, 2026.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- build-system
Research direction
Start by reproducing the failed build and retrying ./case.build after correcting the error; inspect how env_build sets BUILD_STATUS and how ./case.build checks it. Use ./xmlchange BUILD_STATUS=0 only as a comparison. Done means a corrected build can proceed without requiring ./case.build --clean-all.
Written by the indexing model from the issue text.
Description
Brief summary of bug
Using ctsm5.4.060, when a build fails (e.g. due to a syntax error), build_status is set to 1 in env_build. Trying to rebuild after correcting build error is then blocked with the following message:
BUILD_STATUS' has changed from 0 to 1
ERROR: For your changes to take effect, run:
./case.build --clean-all
./case.build
This is undesirable because it forces a complete clean and rebuild, instead of just rebuilding necessary files. A work-around is to manually set build_status to 0 with ./xmlchange BUILD_STATUS=0; then ./case.build can proceed.
General bug information
CTSM version you are using: ctsm5.4.060
Does this bug cause significantly incorrect results in the model's science? No
Configurations affected: anytime the build fails and you have to rerun, because there was a problem in one of the Fortran source files
Details of bug
In the chat discussion, Erik suggests that likely it's the changes that came in with cime6.5.4 that was brought in with ctsm5.4.054. Erik, replicated this in the latest dev version. It only happens when the build fails. But, that's the time that you want it to just rebuild the few files that failed.
Erik will open a corresponding CIME issue.
- Dominant language
- Fortran
- Stars
- 362
- Forks
- 372
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the 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/CTSM
-
b4b code health next
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ESCOMP/CTSM#4330 · 1 comment ·
Maintainers usually reply within 1 day
-
good first issue next size: small test: python usability
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
b4b next size: small
Difficulty 1/5 Under an hour Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Remove ARSLu and ESLgS from the list of available PLUMBER2 sites displayed by running run_tower --helpPossibly taken @samsrabin claimed this 8 days ago. Openb4b good first issue priority: low usability
Difficulty 1/5 Under an hour Newbie friendliness 72/100
ESCOMP/CTSM#4313 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
b4b usability
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nledford/Ladderback#1242 ·
Maintainers usually reply within 1 day
-
[Bug]: memmachine-client and memmachine-server accept any memmachine-common versionPossibly taken @edwinyyyu claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
MemMachine/MemMachine#1990 ·
Maintainers usually reply within 3 days
-
bug cli documentation sev-3
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
CI: pin Windows checks to windows-2022 — windows-latest now ships VS 18 that node-gyp cannot parseOpen
Difficulty 1/5 Under an hour Newbie friendliness 90/100
skytuhua-org/Gen-V1#1213 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
maplibre/maplibre-native#5072 ·
Maintainers usually reply within 1 day