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/clubb_python_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'
using GIT_ASKPASS to set credentials larsongroupsysadmin github token
> 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 afbbe1126523c6ff7a4bb8091f72a242280490ba (refs/remotes/origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f afbbe1126523c6ff7a4bb8091f72a242280490ba # timeout=10
Commit message: "Setting l_diag_Lscale_from_tau to false caused dycoms2_rf01_fixed_sst to start failing the python vs fortran test. The differences were small and occured at a late timestep, so to fix the test I put a limiter on the number of timesteps the test runs."
> git rev-list --no-walk 02babc6b5a46bda3075bf071426fa20bf200a43b # timeout=10