Skip to content

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_ne4_silhs_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 ea8395f7c70bfd95eddb22be9fb66eceb2360377 (refs/remotes/origin/clubb_silhs_devel)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f ea8395f7c70bfd95eddb22be9fb66eceb2360377 # timeout=10
Commit message: "Autoupdated CLUBB_core Commit 56254ef6787724e586ed16a974b53a66539af8a9 Author: bmg929 Date: Fri Apr 5 23:05:24 2024 -0500 The code that advances um and vm when l_predict_upwp_vpwp is turned off (as found in advance_windm_edsclrm) was accessing the ghost point in one spot. I rewrote it in the exact way the code in the clubb_ghost_exorcism branch is written so that it makes the same calculation without referencing the ghost point. I also rewrote a couple stats by outputting a value of 0 at the ghost point to maintain stat consistency between the master and the ghost exorcism branch."
 > git rev-list --no-walk f53ec9c1686e7a2bd01a06b11c96150bf899f2ef # timeout=10