Started by an SCM change Obtained jenkins_tests/cam_BFB_coarse_res_gfortran_test/Jenkinsfile from git https://github.com/larson-group/cam.git [Pipeline] Start of Pipeline [Pipeline] node Still waiting to schedule task Waiting for next available executor Running on overlie in /home/jenkins/workspace/cam_BFB_coarse_res_gfortran_test [Pipeline] { [Pipeline] stage [Pipeline] { (Declarative: Checkout SCM) [Pipeline] checkout The recommended git tool is: git Wiping out workspace first. Cloning the remote Git repository Cloning repository https://github.com/larson-group/cam.git > git init /home/jenkins/workspace/cam_BFB_coarse_res_gfortran_test # timeout=10 Fetching upstream changes from https://github.com/larson-group/cam.git > git --version # timeout=10 > git --version # 'git version 2.34.1' > git fetch --tags --force --progress -- https://github.com/larson-group/cam.git +refs/heads/*:refs/remotes/origin/* # timeout=10 Avoid second fetch Checking out Revision fe5c039b9bba8aa4acb3a124acc0ad44cbe4cf2d (refs/remotes/origin/clubb_silhs_devel) > git config remote.origin.url https://github.com/larson-group/cam.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git rev-parse refs/remotes/origin/clubb_silhs_devel^{commit} # timeout=10 > git config core.sparsecheckout # timeout=10 > git checkout -f fe5c039b9bba8aa4acb3a124acc0ad44cbe4cf2d # timeout=10 Commit message: "Autoupdated CLUBB_core Commit 418c202a9b0512fc8c4f421918cc978164db852d Author: Gunther Huebler Date: Wed Dec 17 14:58:28 2025 -0600 Fixes for fill_holes and edsclr code (#1266) * Fixing bugs in new hole fillers that caused error when ran in descending mode, the issue was that dz is negative in descending mode, so we need abs() around it when calculating the normalized mass. Also fixing a related bug in the way edsclr code calls the hole filler - it was not using the generalized bounds. Also removing the ifdef in favor of normal ifs" > git rev-list --no-walk f1c6a5ece8f3616577a7dca89d68f4fe968ffa86 # timeout=10 [Pipeline] } [Pipeline] // stage [Pipeline] withEnv [Pipeline] { [Pipeline] stage [Pipeline] { (Update sys_admin Repo) [Pipeline] sh + git -C /home/pub/jenkins_BFB_test_configs/sys_admin pull Already up to date. [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Run Python Test) [Pipeline] sh + source /etc/profile.d/larson-group.sh ++ export GIT_EDITOR=vi ++ GIT_EDITOR=vi ++ export SVN_EDITOR=vi ++ SVN_EDITOR=vi ++ export OMP_STACKSIZE=1048579 ++ OMP_STACKSIZE=1048579 ++ export LMOD_ROOT=/opt/lmod/ ++ LMOD_ROOT=/opt/lmod/ ++ source /opt/lmod//lmod/lmod/init/bash +++ '[' -z '' ']' +++ case "$-" in +++ __lmod_vx=x +++ '[' -n x ']' +++ set +x Shell debugging temporarily silenced: export LMOD_SH_DBG_ON=1 for this output (/usr/local/spack/opt/spack/linux-pop22-skylake_avx512/gcc-12.2.0/lmod-8.7.37-fq24mybyn2li6got2bxzk62ejh5d3p4z/lmod/lmod/init/bash) Shell debugging restarted +++ unset __lmod_vx +++ find /usr/local/spack/share/spack/lmod/linux-pop22-x86_64/Core -print -quit ++ export MODULEPATH=/usr/local/spack/share/spack/lmod/linux-pop22-x86_64/Core ++ MODULEPATH=/usr/local/spack/share/spack/lmod/linux-pop22-x86_64/Core + rm -rf /home/jenkins/cam_output/scratch/subcol_SILHS_UWM_debug_f10_f10_mg37 + ulimit -s 8388608 + python3 /home/pub/jenkins_BFB_test_configs/sys_admin/python_nightly_test_suite/run_test.py -c /home/pub/jenkins_BFB_test_configs/cam_BFB_coarse_res_gfortran_test_config ERROR: Illegal case name argument provided Error creating new case argument provided =============================== Configuring Test =============================== Working directory set to: /home/jenkins/workspace/cam_BFB_coarse_res_gfortran_test Checking specified repo: /home/jenkins/workspace/cam_BFB_coarse_res_gfortran_test Using /home/jenkins/workspace/cam_BFB_coarse_res_gfortran_test with origin https://github.com/larson-group/cam.git Output Save Mode: none Using branch: clubb_silhs_devel Making list from 'UnresolvedCommits': CheckRange = False: only comparing baseline to final commit. Run Output Path: /home/jenkins/cam_output/scratch/subcol_SILHS_UWM_debug_f10_f10_mg37/run/subcol_SILHS_UWM_debug_f10_f10_mg37.cam.rh0.0001-01-02-00000.nc Run commands: ['rm -rf /home/jenkins/cam_output/scratch/subcol_SILHS_UWM_debug_f10_f10_mg37', '\nrun_scripts/set_up_repo.py --caseroot /home/$USER/cam_output/caseroot/$CASE --reuse_build --silhs 4 .', '\nrun_scripts/run_cesm_uwm_coarse_res.sh'] Diffing command: python3 run_scripts/netcdf_3D_vars_diff.py =============================== Running Test =============================== Parsing message from commit: fe5c039b9bba8aa4acb3a124acc0ad44cbe4cf2d Checking Commit: fe5c039b9bba8aa4acb3a124acc0ad44cbe4cf2d Running: final commit to check, not labelled BIT_CHANGING Checking out fe5c039b9bba8aa4acb3a124acc0ad44cbe4cf2d Running: 'rm -rf /home/jenkins/cam_output/scratch/subcol_SILHS_UWM_debug_f10_f10_mg37' Running: 'run_scripts/set_up_repo.py --caseroot /home/$USER/cam_output/caseroot/$CASE --reuse_build --silhs 4 .' Running: 'run_scripts/run_cesm_uwm_coarse_res.sh' ================== WARNING ================== Commit: fe5c039b9bba8aa4acb3a124acc0ad44cbe4cf2d There was a problem copying the output. Did the run complete? Is the output path correct? /home/jenkins/cam_output/scratch/subcol_SILHS_UWM_debug_f10_f10_mg37/run/subcol_SILHS_UWM_debug_f10_f10_mg37.cam.rh0.0001-01-02-00000.nc The run will continue, and this commit will be considered unresolved. =========================================== Checking out e2772a10ee0f76ff8e07673ec85e46ccf041c68a Running: 'rm -rf /home/jenkins/cam_output/scratch/subcol_SILHS_UWM_debug_f10_f10_mg37' Running: 'run_scripts/set_up_repo.py --caseroot /home/$USER/cam_output/caseroot/$CASE --reuse_build --silhs 4 .' Running: 'run_scripts/run_cesm_uwm_coarse_res.sh' ================== WARNING ================== Commit: e2772a10ee0f76ff8e07673ec85e46ccf041c68a There was a problem copying the output. Did the run complete? Is the output path correct? /home/jenkins/cam_output/scratch/subcol_SILHS_UWM_debug_f10_f10_mg37/run/subcol_SILHS_UWM_debug_f10_f10_mg37.cam.rh0.0001-01-02-00000.nc The run will continue, and this commit will be considered unresolved. =========================================== ISSUE WITH COMMIT DETECTED: fe5c039b9bba8aa4acb3a124acc0ad44cbe4cf2d differs from e2772a10ee0f76ff8e07673ec85e46ccf041c68a =============================== Test Results =============================== Commit Range Checked = e2772a10ee0f76ff8e07673ec85e46ccf041c68a...fe5c039b9bba8aa4acb3a124acc0ad44cbe4cf2d -- CheckRange was set to False, no intermediate commits checked No new Unresolved commits found. No fake BIT_CHANGING commits found. No remaining Unresolved Commits. =============================== Updating Config File =============================== Saving into UnresolvedCommits: Ignoring fe5c039b9bba8aa4acb3a124acc0ad44cbe4cf2d since it failed to produce output. =============================== Cleanup =============================== Removing all generated output ================== Unresolved Commit Status ================== No remaining Unresolved Commits. ================== FAILED Commits ================== These are the commits which entirely failed to produce output: fe5c039b9bba8aa4acb3a124acc0ad44cbe4cf2d e2772a10ee0f76ff8e07673ec85e46ccf041c68a Exiting with code: 0 [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Declarative: Post Actions) [Pipeline] script [Pipeline] { [Pipeline] sh + chmod -R 755 /home/jenkins/cam_output [Pipeline] } [Pipeline] // script [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline Finished: SUCCESS