Skip to content
[Jenkins]Jenkins
log in
Success

Console Output

Started by an SCM change
Obtained jenkins_tests/cam_BFB_coarse_res_gfortran_test/Jenkinsfile from git https://github.com/larson-group/cam.git
[Pipeline] Start of Pipeline
[Pipeline] node
Still waiting to schedule task
Waiting for next available executor
Running on malan in /home/jenkins/workspace/cam_BFB_coarse_res_gfortran_test
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Declarative: Checkout SCM)
[Pipeline] checkout
The recommended git tool is: git
Wiping out workspace first.
Cloning the remote Git repository
Cloning repository https://github.com/larson-group/cam.git
 > git init /home/jenkins/workspace/cam_BFB_coarse_res_gfortran_test # timeout=10
Fetching upstream changes from https://github.com/larson-group/cam.git
 > git --version # timeout=10
 > git --version # 'git version 2.30.2'
 > git fetch --tags --force --progress -- https://github.com/larson-group/cam.git +refs/heads/*:refs/remotes/origin/* # timeout=10
Avoid second fetch
Checking out Revision c94bc13905bf56ce6e16ec6910e15bab08392572 (refs/remotes/origin/clubb_silhs_devel)
Commit message: "Autoupdated CLUBB_core Commit 8572001d7a87cba485b292f57adfb7abc970e462 Author: Gunther Huebler Date: Fri Nov 22 04:21:52 2024 -0600 Multi col output update (#1211) * Multi_col output update to enable averaging over timesteps and outputting with single precision. This replaces the timestep batched output method used before, which was only noticably faster at low column numbers. This is technically BC (edited during merge, PR no longer BC), because the single precision output will be interpretted as different from the current double precision output."
 > git config remote.origin.url https://github.com/larson-group/cam.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git rev-parse refs/remotes/origin/clubb_silhs_devel^{commit} # timeout=10
 > git config core.sparsecheckout # timeout=10
 > git checkout -f c94bc13905bf56ce6e16ec6910e15bab08392572 # timeout=10
 > git rev-list --no-walk 786953e03d2840b3c737e701024aae136eef8942 # timeout=10
[Pipeline] }
[Pipeline] // stage
[Pipeline] withEnv
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Update sys_admin Repo)
[Pipeline] sh
+ git -C /home/pub/jenkins_BFB_test_configs/sys_admin pull
hint: Pulling without specifying how to reconcile divergent branches is
hint: discouraged. You can squelch this message by running one of the following
hint: commands sometime before your next pull:
hint: 
hint:   git config pull.rebase false  # merge (the default strategy)
hint:   git config pull.rebase true   # rebase
hint:   git config pull.ff only       # fast-forward only
hint: 
hint: You can replace "git config" with "git config --global" to set a default
hint: preference for all repositories. You can also pass --rebase, --no-rebase,
hint: or --ff-only on the command line to override the configured default per
hint: invocation.
Already up to date.
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Run Python Test)
[Pipeline] sh
+ source /etc/profile.d/larson-group.sh
++ export GIT_EDITOR=vi
++ GIT_EDITOR=vi
++ export SVN_EDITOR=vi
++ SVN_EDITOR=vi
++ export OMP_STACKSIZE=1048579
++ OMP_STACKSIZE=1048579
++ export LMOD_ROOT=/opt/lmod/
++ LMOD_ROOT=/opt/lmod/
++ source /opt/lmod//lmod/lmod/init/bash
+++ '[' -z '' ']'
+++ case "$-" in
+++ __lmod_vx=x
+++ '[' -n x ']'
+++ set +x
Shell debugging temporarily silenced: export LMOD_SH_DBG_ON=1 for this output (/usr/local/spack/opt/spack/linux-pop21-skylake_avx512/gcc-12.2.0/lmod-8.7.37-d6vyrvvncsuguygovgvimahv5kfyaunp/lmod/lmod/init/bash)
Shell debugging restarted
+++ unset __lmod_vx
+++ find /usr/local/spack/share/spack/lmod/linux-pop21-x86_64/Core -print -quit
++ export MODULEPATH=/usr/local/spack/share/spack/lmod/linux-pop21-x86_64/Core
++ MODULEPATH=/usr/local/spack/share/spack/lmod/linux-pop21-x86_64/Core
+ rm -rf /home/jenkins/cam_output/scratch/subcol_SILHS_UWM_debug_f10_f10_mg37
+ ulimit -s 8388608
+ python3 /home/pub/jenkins_BFB_test_configs/sys_admin/python_nightly_test_suite/run_test.py -c /home/pub/jenkins_BFB_test_configs/cam_BFB_coarse_res_gfortran_test_config
ERROR: Unknown Job Queue specified use --force to set
submit_jobs case.run
Submit job case.run
Exception from case_run: ERROR: RUN FAIL: Command 'mpirun  -np 2 /home/jenkins/cam_output/scratch/subcol_SILHS_UWM_debug_f10_f10_mg37/bld/cesm.exe   >> cesm.log.$LID 2>&1 ' failed
See log file for details: /home/jenkins/cam_output/scratch/subcol_SILHS_UWM_debug_f10_f10_mg37/run/cesm.log.241123-033520
ERROR: Unknown Job Queue specified use --force to set
submit_jobs case.run
Submit job case.run
Exception from case_run: ERROR: RUN FAIL: Command 'mpirun  -np 2 /home/jenkins/cam_output/scratch/subcol_SILHS_UWM_debug_f10_f10_mg37/bld/cesm.exe   >> cesm.log.$LID 2>&1 ' failed
See log file for details: /home/jenkins/cam_output/scratch/subcol_SILHS_UWM_debug_f10_f10_mg37/run/cesm.log.241123-034104

=============================== Configuring Test ===============================


Working directory set to: /home/jenkins/workspace/cam_BFB_coarse_res_gfortran_test
Checking specified repo: /home/jenkins/workspace/cam_BFB_coarse_res_gfortran_test

Using /home/jenkins/workspace/cam_BFB_coarse_res_gfortran_test with origin https://github.com/larson-group/cam.git

Output Save Mode: none

Using branch: clubb_silhs_devel

Making list from 'UnresolvedCommits':

CheckRange = False: only comparing baseline to final commit.

Run Output Path: /home/jenkins/cam_output/scratch/subcol_SILHS_UWM_debug_f10_f10_mg37/run/subcol_SILHS_UWM_debug_f10_f10_mg37.cam.rh0.0001-01-02-00000.nc

Run commands: ['rm -rf /home/jenkins/cam_output/scratch/subcol_SILHS_UWM_debug_f10_f10_mg37', '\nrun_scripts/set_up_repo.py --caseroot /home/$USER/cam_output/caseroot/$CASE --reuse_build --silhs 4 .', '\nrun_scripts/run_cesm_uwm_coarse_res.sh']

Diffing command: python3 run_scripts/netcdf_3D_vars_diff.py

=============================== Running Test ===============================

Parsing message from commit: c94bc13905bf56ce6e16ec6910e15bab08392572

Checking Commit: c94bc13905bf56ce6e16ec6910e15bab08392572
	Running: final commit to check, not labelled BIT_CHANGING
	Checking out c94bc13905bf56ce6e16ec6910e15bab08392572
	Running: 'rm -rf /home/jenkins/cam_output/scratch/subcol_SILHS_UWM_debug_f10_f10_mg37'
	Running: 'run_scripts/set_up_repo.py --caseroot /home/$USER/cam_output/caseroot/$CASE --reuse_build --silhs 4 .'
	Running: 'run_scripts/run_cesm_uwm_coarse_res.sh'

================== WARNING ==================
Commit:  c94bc13905bf56ce6e16ec6910e15bab08392572

There was a problem copying the output.
Did the run complete?
Is the output path correct? /home/jenkins/cam_output/scratch/subcol_SILHS_UWM_debug_f10_f10_mg37/run/subcol_SILHS_UWM_debug_f10_f10_mg37.cam.rh0.0001-01-02-00000.nc

The run will continue, and this commit will be
considered unresolved.
===========================================
	Checking out 86df31ff4b0640c119437d4690e9556fa4ff36e5
	Running: 'rm -rf /home/jenkins/cam_output/scratch/subcol_SILHS_UWM_debug_f10_f10_mg37'
	Running: 'run_scripts/set_up_repo.py --caseroot /home/$USER/cam_output/caseroot/$CASE --reuse_build --silhs 4 .'
	Running: 'run_scripts/run_cesm_uwm_coarse_res.sh'

================== WARNING ==================
Commit:  86df31ff4b0640c119437d4690e9556fa4ff36e5

There was a problem copying the output.
Did the run complete?
Is the output path correct? /home/jenkins/cam_output/scratch/subcol_SILHS_UWM_debug_f10_f10_mg37/run/subcol_SILHS_UWM_debug_f10_f10_mg37.cam.rh0.0001-01-02-00000.nc

The run will continue, and this commit will be
considered unresolved.
===========================================
	ISSUE WITH COMMIT DETECTED: c94bc13905bf56ce6e16ec6910e15bab08392572 differs from 86df31ff4b0640c119437d4690e9556fa4ff36e5

=============================== Test Results ===============================

Commit Range Checked = 86df31ff4b0640c119437d4690e9556fa4ff36e5...c94bc13905bf56ce6e16ec6910e15bab08392572
-- CheckRange was set to False, no intermediate commits checked

No new Unresolved commits found.

No fake BIT_CHANGING commits found.

No remaining Unresolved Commits.

=============================== Updating Config File ===============================


Saving into UnresolvedCommits: 
Ignoring c94bc13905bf56ce6e16ec6910e15bab08392572 since it failed to produce output.

=============================== Cleanup ===============================

Removing all generated output

================== Unresolved Commit Status ==================

No remaining Unresolved Commits.

================== FAILED Commits ==================

These are the commits which entirely failed to produce output: 
	c94bc13905bf56ce6e16ec6910e15bab08392572
	86df31ff4b0640c119437d4690e9556fa4ff36e5

Exiting with code: 0
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Declarative: Post Actions)
[Pipeline] script
[Pipeline] {
[Pipeline] sh
+ chmod -R 755 /home/jenkins/cam_output
[Pipeline] }
[Pipeline] // script
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Finished: SUCCESS