build_status blocks case rebuild

Abierto
#4,239 5 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@ekluzek ya está trabajando en esto.

Desde el 7/10/2026.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
55/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Área
build-system

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Fortran
Estrellas
362
Forks
372
Merge medio
1 d 11 h
PR fusionados (30 d)
9

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de ESCOMP/CTSM

Todos los issues de ESCOMP/CTSM

Issues similares

Más issues de Build System

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.