Console Output

The recommended git tool is: git
Cloning the remote Git repository
Cloning repository https://github.com/larson-group/sam_clubb.git
 > git init /home/jenkins/workspace/sam_micro_drizzle_intel_test # timeout=10
Fetching upstream changes from https://github.com/larson-group/sam_clubb.git
 > git --version # timeout=10
 > git --version # 'git version 2.30.2'
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/sam_clubb.git +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url https://github.com/larson-group/sam_clubb.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/master^{commit} # timeout=10
Checking out Revision 4e9f7ce77c44f4e45ec2c0c9b6097775ca3956c6 (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 4e9f7ce77c44f4e45ec2c0c9b6097775ca3956c6 # timeout=10
Commit message: "Autoupdated CLUBB_core Commit 18afbb900eaa3202bc48b64daf9daa974ee8dd4c Author: bmg929 Date: Thu Jan 11 14:10:58 2024 -0600 I am altering the mean advection code in preparation for ghost point removal, since the mean advection code incorporates the ghost point in its current calculations. The lower boundary is now treated in the same manner as the upper boundary, where a zero derivative over the boundary is assumed. Any interaction of the current ghost level with the model code is now removed from the mean advection calculation."
 > git rev-list --no-walk 96dce6a9e17a7b5d7ffe283fc5bcbf9bf5028211 # timeout=10