Started by GitHub push by caronlam3763840ff68e6c2b57ebc6de27821892f99503f1b5bd840ff68e6c2b57ebc6de27821892f99503f1b5bdrefs/remotes/origin/main840ff68e6c2b57ebc6de27821892f99503f1b5bd840ff68e6c2b57ebc6de27821892f99503f1b5bdrefs/remotes/origin/main840ff68e6c2b57ebc6de27821892f99503f1b5bd840ff68e6c2b57ebc6de27821892f99503f1b5bdrefs/remotes/origin/maingit@github.com:ISSMteam/ISSM.git0089testReportfalse#376313752702247513Debian Linux - ADOL-C #37633763falsefalse37638459SUCCESS1774651231730https://ross.ics.uci.edu/jenkins/view/Linux/job/Debian_Linux-ADOL-C/3763/Debian_12-VMsrc/c/cores/sealevelchange_core.cpp840ff68e6c2b57ebc6de27821892f99503f1b5bd1774651221000https://ross.ics.uci.edu/jenkins/user/noreplynoreplynoreply@github.comBUG: sealevelchange_core coupler count integer was not reset properly Old bug in coupleroutput_core subroutine, was patched at some point and came back during a failed merge. This effectively prevented the coupling from working beyond time step 1 when runfrequency=1. 2026-03-27 15:40:21 -0700840ff68e6c2b57ebc6de27821892f99503f1b5bdBUG: sealevelchange_core coupler count integer was not reset properlyeditsrc/c/cores/sealevelchange_core.cppgithttps://ross.ics.uci.edu/jenkins/user/noreplynoreply3763https://ross.ics.uci.edu/jenkins/view/Linux/job/Debian_Linux-ADOL-C/AMPI=ampion,label=Debian_12-VM/3763/