Console Output

The recommended git tool is: git
Cloning the remote Git repository
Cloning repository https://github.com/larson-group/cam.git
 > git init /home/jenkins/workspace/cam_scam_gfortran_debug_test # timeout=10
Fetching upstream changes from https://github.com/larson-group/cam.git
 > git --version # timeout=10
 > git --version # 'git version 2.34.1'
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/cam.git +refs/heads/*:refs/remotes/origin/* # timeout=10
Avoid second fetch
Checking out Revision a6e8f378bc25c7cb5627d18a512fc00e8328c873 (refs/remotes/origin/clubb_silhs_devel)
 > 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 a6e8f378bc25c7cb5627d18a512fc00e8328c873 # timeout=10
Commit message: "Autoupdated CLUBB_core Commit 3f865924bdcf798fa45acaa67b57c44f40c32d89 Author: Gunther Huebler Date: Wed Jul 31 17:30:51 2024 -0500 Moving pdf_params copying to copyin. This is the data structure that contains pointers, and these pointers will be different on the host and device, so it is bad in theory to copy the structure back to the CPU as it might overwrite cpu memory pointers with gpu memory pointers. In practice though I've seen no problems caused by this, I'm just making this commit preemptively, and it has already been tested with the ECT test."
 > git rev-list --no-walk c0a710c144a2cb7367fd07d20be1f9ab92757a45 # timeout=10