Console Output

The recommended git tool is: git
Cloning the remote Git repository
Cloning repository https://github.com/larson-group/e3sm.git
 > git init /home/jenkins/workspace/e3sm_run_gfortran_test # timeout=10
Fetching upstream changes from https://github.com/larson-group/e3sm.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/e3sm.git +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url https://github.com/larson-group/e3sm.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 78d63fb15c65b0b70f0c537b44e3f87ec335361b (refs/remotes/origin/clubb_silhs_devel)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 78d63fb15c65b0b70f0c537b44e3f87ec335361b # timeout=10
Commit message: "Autoupdated CLUBB_core Commit be09281d23655b337060e449482df6e6f3f3b919 Author: bmg929 Date: Wed Apr 10 11:59:15 2024 -0500 I am updating the loop in subroutine diagnose_xpwp so that it doesn't loop over the model upper or lower boundaries. Calculations at those levels are irrelevant to the results, and their inclusion causes bitness differences between the master and clubb_ghost_exorcism branches. Since this code change causes differences in the zm stats file at the upper and lower boundaries for a few fields, this commit is technically BIT_CHANGING, although it should be noted that it does not change the simulation results."
 > git rev-list --no-walk 08ebf7b30de887e078b8e812c4cbe2f8acb842df # timeout=10