build_status blocks case rebuild

Aperta
#4,239 5 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@ekluzek ci sta già lavorando.

Dal 7/10/2026.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
55/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Ambito
build-system

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

b4b usability
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.

Lingua principale
Fortran
Stelle
362
Fork
372
Merge medio
1g 11h
PR unite (30g)
9

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ESCOMP/CTSM

Tutte le issue di ESCOMP/CTSM

Issue simili

Altre issue su Build System

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.