Started by GitHub push by caronlam3448840ff68e6c2b57ebc6de27821892f99503f1b5bd840ff68e6c2b57ebc6de27821892f99503f1b5bdrefs/remotes/origin/main840ff68e6c2b57ebc6de27821892f99503f1b5bd840ff68e6c2b57ebc6de27821892f99503f1b5bdrefs/remotes/origin/main840ff68e6c2b57ebc6de27821892f99503f1b5bd840ff68e6c2b57ebc6de27821892f99503f1b5bdrefs/remotes/origin/maingit@github.com:ISSMteam/ISSM.git009testReportfalse#3448384088639719Debian Linux - Ice-Ocean #34483448falsefalse34488467SUCCESS1774652109671https://ross.ics.uci.edu/jenkins/job/debian_linux-ice-ocean/3448/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/noreplynoreply