Console Output

The recommended git tool is: git
Cloning the remote Git repository
Cloning repository https://github.com/larson-group/wrf.git
 > git init /home/jenkins/workspace/wrf_clubb_silhs_parallel_ifort # timeout=10
Fetching upstream changes from https://github.com/larson-group/wrf.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/wrf.git +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url https://github.com/larson-group/wrf.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 c75ade879c147bd52ca70a050e2aaa034fd5bf7d (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f c75ade879c147bd52ca70a050e2aaa034fd5bf7d # timeout=10
Commit message: "Autoupdated CLUBB_core Commit 45b34a9553d7741f7f6f057941c82b20801c1751 Author: bmg929 Date: Fri Apr 5 01:04:20 2024 -0500 At the ghost point below the surface, which does not matter in the calculations, a value of 0 is now being entered for thermodynamic-level output stats coef_wprtp2_implicit, term_wprtp2_explicit, etc. Why would we do this? The answer is Why Not??!!!!"
 > git rev-list --no-walk db9c58f56da61b0d60081a28ca08136b5997381f # timeout=10