Started by an SCM change
Obtained jenkins_tests/clubb_api_commitment_test/Jenkinsfile from git <a href='https://github.com/larson-group/clubb.git'>https://github.com/larson-group/clubb.git</a>
<span class="pipeline-new-node" nodeId="2" startId="2">[Pipeline] Start of Pipeline
</span><span class="pipeline-new-node" nodeId="3" startId="3" enclosingId="2">[Pipeline] node
</span><span class="pipeline-node-3">Running on <a href='/jenkins/computer/(built-in)/' class='jenkins-table__link model-link model-link--float'>Jenkins</a> in /home/jenkins/workspace/clubb_api_commitment_test
</span><span class="pipeline-new-node" nodeId="4" startId="4" enclosingId="3">[Pipeline] {
</span><span class="pipeline-new-node" nodeId="5" startId="5" enclosingId="4">[Pipeline] stage
</span><span class="pipeline-new-node" nodeId="6" startId="6" enclosingId="5" label="Declarative: Checkout SCM">[Pipeline] { (Declarative: Checkout SCM)
</span><span class="pipeline-new-node" nodeId="7" enclosingId="6">[Pipeline] checkout
</span><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 2.34.1'
using GIT_ASKPASS to set credentials A token based key used by Jenkins to preform Github actions, created 6/21/2021
 &gt; git fetch --tags --force --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 9136bf065fe59e64db24c8a3f2aeee7178450273 (refs/remotes/origin/master)
 &gt; git config core.sparsecheckout # timeout=10
 &gt; git checkout -f 9136bf065fe59e64db24c8a3f2aeee7178450273 # timeout=10
Commit message: "I'm changing the way ddzt handles the derivative over momentum level 1. Previously, it was based on the differential between the ghost point and the first level above the surface. Now, the value of the derivative at momentum level 2 is simply being dropped down to momentum level 1."
 &gt; git rev-list --no-walk 3d364fec45434074a7d9d1815861b4ff8d6df674 # timeout=10
</span><span class="pipeline-new-node" nodeId="8" startId="6">[Pipeline] }
</span><span class="pipeline-new-node" nodeId="9" startId="5">[Pipeline] // stage
</span><span class="pipeline-new-node" nodeId="10" startId="10" enclosingId="4">[Pipeline] withEnv
</span><span class="pipeline-new-node" nodeId="11" startId="11" enclosingId="10">[Pipeline] {
</span><span class="pipeline-new-node" nodeId="12" startId="12" enclosingId="11">[Pipeline] stage
</span><span class="pipeline-new-node" nodeId="13" startId="13" enclosingId="12" label="Run the API Commitment Script">[Pipeline] { (Run the API Commitment Script)
</span><span class="pipeline-new-node" nodeId="14" enclosingId="13">[Pipeline] sh
</span><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'...
Updating files:  71% (1798/2504)
Updating files:  72% (1803/2504)
Updating files:  73% (1828/2504)
Updating files:  74% (1853/2504)
Updating files:  75% (1878/2504)
Updating files:  76% (1904/2504)
Updating files:  77% (1929/2504)
Updating files:  78% (1954/2504)
Updating files:  79% (1979/2504)
Updating files:  80% (2004/2504)
Updating files:  81% (2029/2504)
Updating files:  82% (2054/2504)
Updating files:  83% (2079/2504)
Updating files:  84% (2104/2504)
Updating files:  85% (2129/2504)
Updating files:  86% (2154/2504)
Updating files:  87% (2179/2504)
Updating files:  88% (2204/2504)
Updating files:  89% (2229/2504)
Updating files:  90% (2254/2504)
Updating files:  91% (2279/2504)
Updating files:  92% (2304/2504)
Updating files:  93% (2329/2504)
Updating files:  94% (2354/2504)
Updating files:  95% (2379/2504)
Updating files:  96% (2404/2504)
Updating files:  97% (2429/2504)
Updating files:  98% (2454/2504)
Updating files:  99% (2479/2504)
Updating files: 100% (2504/2504)
Updating files: 100% (2504/2504), done.
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
Copying the SILHS API into the CLUBB API
Running the Usage Analyzer
  File "/home/jenkins/workspace/clubb_api_commitment_test/utilities/api_analysis/usage_analyzer.py", line 414
    print ""
    ^^^^^^^^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print(...)?
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
  File "/home/jenkins/workspace/clubb_api_commitment_test/utilities/api_analysis/api_commitment_test.py", line 109
    print "An API error occurred in ", file, errorDictionary[file]
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print(...)?
Testing CLUBB_core's API Commitment
  File "/home/jenkins/workspace/clubb_api_commitment_test/utilities/api_analysis/api_commitment_test.py", line 109
    print "An API error occurred in ", file, errorDictionary[file]
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print(...)?
Testing SAM's API Commitment
  File "/home/jenkins/workspace/clubb_api_commitment_test/utilities/api_analysis/api_commitment_test.py", line 109
    print "An API error occurred in ", file, errorDictionary[file]
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print(...)?
Testing CAM's API Commitment
  File "/home/jenkins/workspace/clubb_api_commitment_test/utilities/api_analysis/api_commitment_test.py", line 109
    print "An API error occurred in ", file, errorDictionary[file]
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print(...)?
Testing WRF's API Commitment
  File "/home/jenkins/workspace/clubb_api_commitment_test/utilities/api_analysis/api_commitment_test.py", line 109
    print "An API error occurred in ", file, errorDictionary[file]
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print(...)?
  File "/home/jenkins/workspace/clubb_api_commitment_test/utilities/api_analysis/create_module_table.py", line 76
    print datetime.datetime.now()
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print(...)?
Removing Checkouts
Testing API Commitment
All host models passed.
Removing Dependencies
</span><span class="pipeline-new-node" nodeId="15" startId="13">[Pipeline] }
</span><span class="pipeline-new-node" nodeId="16" startId="12">[Pipeline] // stage
</span><span class="pipeline-new-node" nodeId="17" startId="17" enclosingId="11">[Pipeline] stage
</span><span class="pipeline-new-node" nodeId="18" startId="18" enclosingId="17" label="Display Tables">[Pipeline] { (Display Tables)
</span><span class="pipeline-new-node" nodeId="19" enclosingId="18">[Pipeline] sh
</span><span class="pipeline-node-19">+ cat utilities/api_analysis/log/apiCommitmentTable.txt
</span><span class="pipeline-new-node" nodeId="20" enclosingId="18">[Pipeline] sh
</span><span class="pipeline-node-20">+ cat utilities/api_analysis/log/usageAnalyzerTable.txt
</span><span class="pipeline-new-node" nodeId="21" startId="18">[Pipeline] }
</span><span class="pipeline-new-node" nodeId="22" startId="17">[Pipeline] // stage
</span><span class="pipeline-new-node" nodeId="23" startId="23" enclosingId="11">[Pipeline] stage
</span><span class="pipeline-new-node" nodeId="24" startId="24" enclosingId="23" label="Declarative: Post Actions">[Pipeline] { (Declarative: Post Actions)
</span><span class="pipeline-new-node" nodeId="25" startId="25" enclosingId="24">[Pipeline] script
</span><span class="pipeline-new-node" nodeId="26" startId="26" enclosingId="25">[Pipeline] {
</span><span class="pipeline-new-node" nodeId="27" enclosingId="26">[Pipeline] cleanWs
</span><span class="pipeline-node-27">[WS-CLEANUP] Deleting project workspace...
[WS-CLEANUP] Deferred wipeout is used...
[WS-CLEANUP] done
</span><span class="pipeline-new-node" nodeId="28" startId="26">[Pipeline] }
</span><span class="pipeline-new-node" nodeId="29" startId="25">[Pipeline] // script
</span><span class="pipeline-new-node" nodeId="30" startId="24">[Pipeline] }
</span><span class="pipeline-new-node" nodeId="31" startId="23">[Pipeline] // stage
</span><span class="pipeline-new-node" nodeId="32" startId="11">[Pipeline] }
</span><span class="pipeline-new-node" nodeId="33" startId="10">[Pipeline] // withEnv
</span><span class="pipeline-new-node" nodeId="34" startId="4">[Pipeline] }
</span><span class="pipeline-new-node" nodeId="35" startId="3">[Pipeline] // node
</span><span class="pipeline-new-node" nodeId="36" startId="2">[Pipeline] End of Pipeline
</span>Finished: SUCCESS