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
 > 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
Avoid second fetch
 > git rev-parse refs/remotes/origin/clubb_silhs_devel^{commit} # timeout=10
Checking out Revision 6f0563a327d1cfefda2306f4c6d51ff65557810f (refs/remotes/origin/clubb_silhs_devel)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 6f0563a327d1cfefda2306f4c6d51ff65557810f # timeout=10
Commit message: "Autoupdated CLUBB_core Commit b01f0e8e8f1ed4635a6c8cbef0f0a730351305b2 Author: bmg929 Date: Tue Mar 11 17:12:02 2025 -0500 The generalized grid test should not output a clubb fatal error when it fails. Rather, they should output a unique error code specific to their failure. Otherwise, failures due to numerical instability, etc., will be confused as generalized grid failures in the Jenkins tests."
 > git rev-list --no-walk 7bca04893f00be9db88d9833009e0e88bf1a1647 # timeout=10