fix in case spack.lock doesn't exist

.gitlab-ci.yml

@@ -183,8 +183,6 @@ build-spack-env-on-runner:
     - spack repo add .
     - spack env create $SPACK_DEV_ENV spack.yaml
     - spack env activate $SPACK_DEV_ENV
-    # see comments in sync-gitlab-spack-instance
-    - rm $SPACK_ROOT/var/spack/environments/$SPACK_DEV_ENV/spack.lock
     - spack install -y -j2 --fresh --no-check-signature --test root
   after_script:
     - mkdir spack_logs
@@ -248,7 +246,7 @@ sync-gitlab-spack-instance:
     - cp $CI_PROJECT_DIR/spack.yaml $SPACK_ROOT/var/spack/environments/$SPACK_NFS_ENV/spack.yaml
     # 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
+    - 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 module tcl refresh -y
     - spack reindex