From d1c024e1b9ca012a8a1c49e98e363db0b56134cb Mon Sep 17 00:00:00 2001
From: Eleni Mathioulaki <emathioulaki@athenarc.gr>
Date: Wed, 1 Mar 2023 17:49:39 +0100
Subject: [PATCH] remove --overwrite
---
.gitlab-ci.yml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 43bd9e9c..6463b5b3 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -186,7 +186,7 @@ build-spack-env-on-runner:
- spack repo add .
- spack env create $SPACK_DEV_ENV spack.yaml
- spack env activate $SPACK_DEV_ENV
- - spack install --overwrite -y -j2 --fresh --test root
+ - spack install -y -j2 --fresh --test root
after_script:
- mkdir spack_logs
- |
@@ -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 --overwrite -y -j2 --fresh --test root
+ - spack install -y -j2 --fresh --test root
- spack module tcl refresh -y
- spack reindex
- spack env loads -r
--
GitLab