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 ef9b29cdca2610dab053c11295a8144d74ab62f8 (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f ef9b29cdca2610dab053c11295a8144d74ab62f8 # timeout=10
Commit message: "Autoupdated CLUBB_core Commit d0a28efd5a173fe59114e69f16d999ab31cc6080 Author: bmg929 Date: Thu Dec 21 09:55:34 2023 -0600 With wp3 now being set to a fixed-point boundary condition value of 0 at the current thermodynamic level 2 (first t-lev above the surface), it is not necessary to loop over level 2 within the code for each wp3 term. This commit is BIT_CHANGING, but only for the wp3 budget terms (e.g. wp3_ta) in the zt output file at level k = 2. It doesn't change the actual answer. All other variables are bit-for-bit identical."
 > git rev-list --no-walk 075770dd8cfd26e5f05694556450a9019d04d5e2 # timeout=10