Started by an SCM change
Obtained jenkins_tests/api_commitment_test/Jenkinsfile from git <a href='https://github.com/larson-group/clubb.git'>https://github.com/larson-group/clubb.git</a>
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] Start of Pipeline
[Pipeline] node
<span class="pipeline-node-3">Running on Jenkins in /home/jenkins/workspace/clubb_api_commitment_test
</span>[Pipeline] {
[Pipeline] stage
[Pipeline] { (Declarative: Checkout SCM)
[Pipeline] checkout
<span class="pipeline-node-7">The recommended git tool is: git
Cloning the remote Git repository
Cloning repository <a href='https://github.com/larson-group/clubb.git'>https://github.com/larson-group/clubb.git</a>
 &gt; git init /home/jenkins/workspace/clubb_api_commitment_test # timeout=10
Fetching upstream changes from <a href='https://github.com/larson-group/clubb.git'>https://github.com/larson-group/clubb.git</a>
 &gt; git --version # timeout=10
 &gt; git --version # 'git version 1.8.3.1'
using GIT_ASKPASS to set credentials THe key used by the system for the tests
 &gt; git fetch --tags --progress <a href='https://github.com/larson-group/clubb.git'>https://github.com/larson-group/clubb.git</a> +refs/heads/*:refs/remotes/origin/* # timeout=10
 &gt; git config remote.origin.url <a href='https://github.com/larson-group/clubb.git'>https://github.com/larson-group/clubb.git</a> # timeout=10
 &gt; git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
Avoid second fetch
 &gt; git rev-parse refs/remotes/origin/master^{commit} # timeout=10
Checking out Revision 0e8ed5d48b7be5f98b78abc60c44627a5c8cf050 (refs/remotes/origin/master)
 &gt; git config core.sparsecheckout # timeout=10
 &gt; git checkout -f 0e8ed5d48b7be5f98b78abc60c44627a5c8cf050 # timeout=10
Commit message: "Removing "if" statement around calculation of wp4 in pdf_closure_module.F90 and the same "if" statement around some further manipulation of wp4 in advance_clubb_core.  Results are bit-for-bit with this change, since normally all cases calculate wp4 anyway since the "if" condition was always satisfied in normal runs (but not, for example, in some tuning runs).  This was done because the new wp3_pr_dfsn term needs wp4 in its current formulation so it needs to always be calculated."
 &gt; git rev-list --no-walk 103b65d48c57146ed63a900c901fa0f0f62aefb7 # timeout=10
</span>[Pipeline] }
[Pipeline] // stage
[Pipeline] withEnv
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Run the API Commitment Script)
[Pipeline] sh
<span class="pipeline-node-14">+ utilities/api_analysis/run_full_api_diagnostics.bash
Checking out CLUBB
Cloning into 'CLUBB'...
Checking out SAM
Cloning into 'SAM'...
Checking out WRF
Cloning into 'WRF'...
Checking out CAM
Cloning into 'CAM'...
Moving CLUBB_core
Removing .git Folders
find: ‘CLUBB/.git’: No such file or directory
find: ‘SAM/.git’: No such file or directory
find: ‘WRF/.git’: No such file or directory
find: ‘CAM/.git’: No such file or directory
Removing API from CLUBB_core
Removing API from SILHS
Removing G_Unit_Tests from CLUBB
Moving SILHS to CLUBB_core
Testing CLUBB_Standalone's API Commitment
Testing CLUBB_core's API Commitment
Testing SAM's API Commitment
Testing CAM's API Commitment
Testing WRF's API Commitment
Removing Checkouts
Testing API Commitment
All host models passed.
Removing Dependencies
</span>[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Declarative: Post Actions)
[Pipeline] cleanWs
<span class="pipeline-node-19">[WS-CLEANUP] Deleting project workspace...
[WS-CLEANUP] Deferred wipeout is used...
[WS-CLEANUP] done
</span>[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Finished: SUCCESS