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
Avoid second fetch
Checking out Revision 96fddf1f5374af3f79f856d0bad01e97dc997a52 (refs/remotes/origin/clubb_silhs_devel)
Commit message: "Autoupdated CLUBB_core Commit 77d989d6d7397187825e263ed404e956c7598749 Author: Gunther Huebler Date: Thu May 14 13:30:26 2026 -0500 This fixes the GPU BFB test that failed due to stats-only differences in rtm_ed and thlm_ed, and as a result is technically BIT_CHANGING. Also, the BFB with varying flags failed because flag set 1 changed to use the lapack solvers since the custom ones it set before are now default. RESOLVED:34c6bb07afb6e445f60ea87dcc632969086f9fa1"
> 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 96fddf1f5374af3f79f856d0bad01e97dc997a52 # timeout=10
> git rev-list --no-walk 336d2cb61a2fef8d3142baae1718ec093511572d # timeout=10
