Console Output

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_gpu_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
 > 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
Avoid second fetch
 > git rev-parse refs/remotes/origin/clubb_silhs_devel^{commit} # timeout=10
Checking out Revision d36be159c18259ab980e9814ce1dbb17508af840 (refs/remotes/origin/clubb_silhs_devel)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f d36be159c18259ab980e9814ce1dbb17508af840 # timeout=10
Commit message: "Autoupdated CLUBB_core Commit 5e3cfdd6efddf098dbddb41a5848e3ef4189aac8 Author: Gunther Huebler Date: Tue May 5 17:13:07 2026 -0500 Fixing python api and python/jax driver. Also fixing bug that caused non-BFBness in stats outputs (only upwp_cl/vpwp_cl) when using l_predict_upwp_vpwp=.false., and adding ulimit -s 8388608 to fix GPU test (though it's unclear why exactly we need this all of a sudden for this test). RESOLVED:643d128a5613019595aecd643f1028e937ad4b76 RESOLVED:f146255f50732c445ccbd012ca45888a9ce44d0b, and since this changes stats this is technically BIT_CHANGING"
 > git rev-list --no-walk 38654cc55216941b4e406952b7b32367260c4885 # timeout=10