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_debug_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
Avoid second fetch
Checking out Revision f10cbbaf6b8f6602e1451fbeeef59f2a52614b44 (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 f10cbbaf6b8f6602e1451fbeeef59f2a52614b44 # timeout=10
Commit message: "Autoupdated CLUBB_core Commit c9083983343f851915dccdd10d7d6ff7baad24b3 Author: bmg929 Date: Tue Jul 16 22:49:25 2024 -0500 I am committing changes to stats output for cloud_cover, rcm_in_layer, and z_cloud base owing to the gymnastics it takes to avoid the ghost point in calculations. These changes are BIT_CHANGING, but they don't change the answer."
 > git rev-list --no-walk 67d9ce698f80c739db2dbe35f43c96a20b8270b1 # timeout=10