Adds two options for using pinned versions in swell experiments:
Adds pinned_create jedi build method. Calling this method will clone jedi repositories with hashes in pinned_versions.yaml. Then it will build jedi and proceed as normal.
Adds use_pinned_existing jedi build method. This will point to build and source directories in /discover/nobackup/projects/gmao/advda/pinned_jedi_bundle. This build is currently pinned to August 31st. The check_hashes script is called to check if commit hashes in this build lines up with pinned_versions.yaml. If it does not, it will abort. If it does, it will proceed as normal.
Note that none of these options are default and they must be indicated through the CLI.
Decide whether to go ahead and build Jedi if use_pinned_existing fails. Note that if this happens, user can just rerun the experiment with pinned_create instead.
Description
Adds two options for using pinned versions in swell experiments:
pinned_create
jedi build method. Calling this method will clone jedi repositories with hashes inpinned_versions.yaml
. Then it will build jedi and proceed as normal.use_pinned_existing
jedi build method. This will point tobuild
andsource
directories in/discover/nobackup/projects/gmao/advda/pinned_jedi_bundle
. This build is currently pinned to August 31st. Thecheck_hashes
script is called to check if commit hashes in this build lines up withpinned_versions.yaml
. If it does not, it will abort. If it does, it will proceed as normal.Note that none of these options are default and they must be indicated through the CLI.
Additional changes:
Removing GEOS_mksi main branch test since main and develop are now synced: https://github.com/GEOS-ESM/GEOS_mksi/pull/2this is addressed in Alexey's PR #436Issues
Resolves #423 Addresses some concerns in #345
TODO:
use_pinned_existing
fails. Note that if this happens, user can just rerun the experiment withpinned_create
instead.