Console Output

The recommended git tool is: git
Cloning the remote Git repository
Cloning repository https://github.com/larson-group/cam.git
 > git init /home/jenkins/workspace/cam_scam_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'
using GIT_ASKPASS to set credentials A token based key used by Jenkins to preform Github actions, created 6/21/2021
 > 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 ddd334ee5c7d9ce02588dce06ab537065670fbcf (refs/remotes/origin/clubb_silhs_devel)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f ddd334ee5c7d9ce02588dce06ab537065670fbcf # timeout=10
Commit message: "Autoupdated CLUBB_core Commit 3b3339a9e9932452f21db516965e9b7e379a2228 Author: bmg929 Date: Thu May 2 16:30:56 2024 -0500 I am moving the advance_xm_wpxp setting of xm(1) = xm(2) from the end of xm_clipping_and_stats to the very end of advance_xm_wpxp, right before the return to advance_clubb_core. The reason I am doing this is the nudging was done after setting xm(1) = xm(2) and would alter the results. This is no longer the case, as setting xm(1) = xm(2) is now being done after nudging. This is being done in advance of removal of the ghost point from CLUBB. This helps ensure a bit-for-bit match between the ghost exorcism branch and the master branch."
 > git rev-list --no-walk 6f02cf7b06690e57b01c9761f5a59770aace941a # timeout=10