The recommended git tool is: git
Cloning the remote Git repository
Cloning repository https://github.com/larson-group/clubb.git
> git init /home/jenkins/workspace/clubb_restart_silhs_gfortran_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/master^{commit} # timeout=10
Checking out Revision fb12cc1c0be895d2db030ceed981bc5121277b0e (refs/remotes/origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f fb12cc1c0be895d2db030ceed981bc5121277b0e # timeout=10
Commit message: "The last commit should've been marked as non-BFB since it corrected a crashing bug - so comparing output to no output caused the output to be considered different. This was missed because the BFB checking tests didn't fail, and that was because the commit that caused the crashing was marked non-BFB, so an unusual combo. In general though any commit that fixes crashing behavior should be labelled as bit changing. RESOLVED:73dc365c77ab4bf2405d753f167307ae9be330a0"
> git rev-list --no-walk 73dc365c77ab4bf2405d753f167307ae9be330a0 # timeout=10
