Started by user <a href='/jenkins/user/sdomke' class='jenkins-table__link model-link model-link--float'>Steffen Domke</a>
Obtained jenkins_tests/clubb_BFB_r8029_flags_gfortran_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/mitch/' class='jenkins-table__link model-link model-link--float'>mitch</a> in /home/jenkins/workspace/clubb_BFB_r8029_flags_gfortran_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
Wiping out workspace first.
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_BFB_r8029_flags_gfortran_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'
 &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
Avoid second fetch
Checking out Revision fa5edf3c9549a7bf9b076506514aa7445f322c43 (refs/remotes/origin/master)
Commit message: "Since the call to adj_low_res_nu is not tested by CLUBB's main ascending vs descending grid test (since it is not called from within advance_clubb_core or from SILHS), I added it to the reverse grid direction G Unit test so that the results from ascending vs. descending grids get checked."
 &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
 &gt; git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 &gt; git config core.sparsecheckout # timeout=10
 &gt; git checkout -f fa5edf3c9549a7bf9b076506514aa7445f322c43 # timeout=10
 &gt; git rev-list --no-walk fa5edf3c9549a7bf9b076506514aa7445f322c43 # 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="Update sys_admin Repo">[Pipeline] { (Update sys_admin Repo)
</span><span class="pipeline-new-node" nodeId="14" enclosingId="13">[Pipeline] sh
</span><span class="pipeline-node-14">+ git -C /home/pub/jenkins_BFB_test_configs/sys_admin pull
fatal: cannot change to '/home/pub/jenkins_BFB_test_configs/sys_admin': Input/output error
</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="Run Python Test">[Pipeline] { (Run Python Test)
</span>Stage "Run Python Test" skipped due to earlier failure(s)
<span class="pipeline-new-node" nodeId="19" enclosingId="18">[Pipeline] getContext
</span><span class="pipeline-new-node" nodeId="20" startId="18">[Pipeline] }
</span><span class="pipeline-new-node" nodeId="21" startId="17">[Pipeline] // stage
</span><span class="pipeline-new-node" nodeId="22" startId="22" enclosingId="11">[Pipeline] stage
</span><span class="pipeline-new-node" nodeId="23" startId="23" enclosingId="22" label="Declarative: Post Actions">[Pipeline] { (Declarative: Post Actions)
</span><span class="pipeline-new-node" nodeId="24" startId="24" enclosingId="23">[Pipeline] script
</span><span class="pipeline-new-node" nodeId="25" startId="25" enclosingId="24">[Pipeline] {
</span><span class="pipeline-new-node" nodeId="26" enclosingId="25">[Pipeline] emailext
</span><span class="pipeline-node-26">Sending email to: messnermet@uwm.edu
</span><span class="pipeline-new-node" nodeId="27" startId="25">[Pipeline] }
</span><span class="pipeline-new-node" nodeId="28" startId="24">[Pipeline] // script
</span><span class="pipeline-new-node" nodeId="29" startId="23">[Pipeline] }
</span><span class="pipeline-new-node" nodeId="30" startId="22">[Pipeline] // stage
</span><span class="pipeline-new-node" nodeId="31" startId="11">[Pipeline] }
</span><span class="pipeline-new-node" nodeId="32" startId="10">[Pipeline] // withEnv
</span><span class="pipeline-new-node" nodeId="33" startId="4">[Pipeline] }
</span><span class="pipeline-new-node" nodeId="34" startId="3">[Pipeline] // node
</span><span class="pipeline-new-node" nodeId="35" startId="2">[Pipeline] End of Pipeline
</span>ERROR: script returned exit code 128
Finished: FAILURE