Skip to content
Snippets Groups Projects
Commit c5adf1ff authored by Eleni Mathioulaki's avatar Eleni Mathioulaki
Browse files

remove `--no-check-signature` everywhere

parent 4c6b7831
No related branches found
No related tags found
2 merge requests!301create new experimental release,!300add spack post-installation testing
Pipeline #21372 waiting for manual action with stage
in 6 seconds
......@@ -261,7 +261,7 @@ sync-gitlab-spack-instance:
# There is a known spack bug (https://github.com/spack/spack/issues/29447) in installing test dependencies for installation tests. The workaround suggested
# in the issue is to NOT concretize separately, but simply remove the .lock file and let the enironment be concretized by the spack install command:
- rm $SPACK_ROOT/var/spack/environments/$SPACK_NFS_ENV/spack.lock || echo "No spack.lock file"
- spack install -y -j2 --fresh --no-check-signature --test root
- spack install -y -j2 --fresh --test root
- spack module tcl refresh -y
- spack reindex
- spack env loads -r
......
......@@ -54,7 +54,7 @@ spack env activate $EBRAINS_SPACK_ENV
# remove the .lock file and let the enironment be concretized by the spack install command:
rm $SPACK_ROOT/var/spack/environments/$EBRAINS_SPACK_ENV/spack.lock || echo "No spack.lock file"
# install the environment, use 2 jobs to reduce the amount of required RAM
spack install -y -j2 --fresh --no-check-signature --test root
spack install -y -j2 --fresh --test root
# rebuild spack's database
spack reindex
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment