Skip to content

Console Output

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_backwards_compatibility_gfortran_test # timeout=10
Fetching upstream changes from https://github.com/larson-group/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/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 f4277535627c705e8851dc3112160fd415252042 (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f f4277535627c705e8851dc3112160fd415252042 # timeout=10
Commit message: "Limiting mpace_b to 250 timestpes for gpu vs cpu test. The mpace_b test passed on my home GPU (RTX 3080), but not when run in jenkens on nelson (P4000). So either the tolerance is too strict, or we're running too many timesteps for mpace_b. Currently the largest difference on mpace_b multicol check is 3.31551e-05 on jenkins, so if this fails also I'll up the tolerance for mpace_b instead of further reducing timesteps run."
 > git rev-list --no-walk dd59f60c668e6989bf231b72032771c3ac9518d5 # timeout=10