Console Output

The recommended git tool is: git
Wiping out workspace first.
Cloning the remote Git repository
Cloning repository https://github.com/larson-group/cam.git
 > git init /home/jenkins/workspace/cam_plot_scam_ifort # timeout=10
Fetching upstream changes from https://github.com/larson-group/cam.git
 > git --version # timeout=10
 > git --version # 'git version 2.34.1'
 > git fetch --tags --force --progress -- https://github.com/larson-group/cam.git +refs/heads/*:refs/remotes/origin/* # timeout=10
Avoid second fetch
Checking out Revision 4bb5edc64d1b8adfee7fd9cd778c3eb1d78181e5 (refs/remotes/origin/clubb_silhs_devel)
Commit message: "Autoupdated CLUBB_core Commit 4c5fa8ce8f53dd868b93cd477e50d8f23bfd9fd8 Author: bmg929 Date: Tue Mar 4 19:57:09 2025 -0600 Hopefully this helps the cpu vs. gpu tests."
 > git config remote.origin.url https://github.com/larson-group/cam.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git rev-parse refs/remotes/origin/clubb_silhs_devel^{commit} # timeout=10
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 4bb5edc64d1b8adfee7fd9cd778c3eb1d78181e5 # timeout=10
 > git rev-list --no-walk 17ee8497050dc3f2a9d872853a0d8c13454e7af8 # timeout=10