The recommended git tool is: git
Wiping out workspace first.
Cloning the remote Git repository
Cloning repository https://github.com/larson-group/sam_clubb.git
> git init /home/jenkins/workspace/sam_clubb_nvhpc_build # timeout=10
Fetching upstream changes from https://github.com/larson-group/sam_clubb.git
> git --version # timeout=10
> git --version # 'git version 2.34.1'
> git fetch --tags --force --progress -- https://github.com/larson-group/sam_clubb.git +refs/heads/*:refs/remotes/origin/* # timeout=10
Avoid second fetch
Checking out Revision be4ba9e2d1614f2681b8479a753f8ea6de3802b9 (refs/remotes/origin/master)
> git config remote.origin.url https://github.com/larson-group/sam_clubb.git # timeout=10
> git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
> git rev-parse refs/remotes/origin/master^{commit} # timeout=10
> git config core.sparsecheckout # timeout=10
> git checkout -f be4ba9e2d1614f2681b8479a753f8ea6de3802b9 # timeout=10
Commit message: "Autoupdated CLUBB_core Commit 7b5214a7a0382d3b5d2df0f7b8a8f11bd11f4bdb Author: Gunther Huebler Date: Tue May 26 16:56:18 2026 -0500 Clubb organization part2 (#1304) A number of fields were being calculated in `advance_clubb_core` (`wp2_zt` `wp3_on_wp2` `wp3_on_wp2_zt` `Skw_zm` `Skw_zt) then passed into other routines, however, all these fields depend on `wp2` and were not being updated after `wp2` was being updated by `calc_sfc_varnce`. This commit fixes that by moving where these fields are calculated - instead of computing in `advance_clubb_core` with the incoming `wp2`, we now calculate them on-demand where they are needed using the most recent value of `wp2`."
> git rev-list --no-walk 1f7243e0875d734b8ab31cdbbc33e2d29af11b01 # timeout=10
