Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
ebrains-spack-builds
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Wiki
Code
Merge requests
0
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
"README.md" did not exist on "a39828c5998b7392d2735b50645e009f7fd3eabd"
Show more breadcrumbs
Klaus Noelp
ebrains-spack-builds
Commits
794618dd
Commit
794618dd
authored
2 years ago
by
Eleni Mathioulaki
Browse files
Options
Downloads
Patches
Plain Diff
add installation-time tests to install_spack_env.sh
parent
2f5ad3f8
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
install_spack_env.sh
+5
-3
5 additions, 3 deletions
install_spack_env.sh
with
5 additions
and
3 deletions
install_spack_env.sh
+
5
−
3
View file @
794618dd
...
...
@@ -48,10 +48,12 @@ fi
# activate environment
cp
$EBRAINS_REPO
/spack.yaml
$SPACK_ROOT
/var/spack/environments/
$EBRAINS_SPACK_ENV
/spack.yaml
spack
env
activate
$EBRAINS_SPACK_ENV
# remove any existing concrete specs from spack.lock and re-concretize everything
spack concretize
--fresh
--force
# 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/
$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
--fresh
--no-check-signature
-
y
-j2
spack
install
-y
-j2
--fresh
--no-check-signature
-
-test
root
# create modules files with spack
spack module tcl refresh
-y
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment