Console Output

The recommended git tool is: git
Wiping out workspace first.
Cloning the remote Git repository
Cloning repository https://github.com/larson-group/clubb.git
 > git init /home/jenkins/workspace/branch_clubb_test # timeout=10
Fetching upstream changes from https://github.com/larson-group/clubb.git
 > git --version # timeout=10
 > git --version # 'git version 2.34.1'
 > git fetch --tags --force --progress -- https://github.com/larson-group/clubb.git +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url https://github.com/larson-group/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/clubb_test_correct_gg^{commit} # timeout=10
Checking out Revision 7543b61da624bfdb0500eb4837d4851385cd11ef (refs/remotes/origin/clubb_test_correct_gg)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 7543b61da624bfdb0500eb4837d4851385cd11ef # timeout=10
Commit message: "Updated the code to use break or return when clubb fatal error is encountered, which is more consistent with the way CLUBB does business now, then simply Fortran stop in place. This also allows the generalized grid test to finally pass for all cases and all flag sets."