Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
A
autoicon
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
w2w
autoicon
Commits
14c9cd5c
Commit
14c9cd5c
authored
1 year ago
by
Oriol Tintó
Browse files
Options
Downloads
Patches
Plain Diff
Using a fixed release of spack instead the development branch.
parent
cdd77170
Loading
Loading
No related merge requests found
Pipeline
#19634
failed
1 year ago
Stage: clean
Stage: build
Stage: run_tests
Changes
1
Pipelines
7
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
conf/common/build.yml
+1
-1
1 addition, 1 deletion
conf/common/build.yml
with
1 addition
and
1 deletion
conf/common/build.yml
+
1
−
1
View file @
14c9cd5c
...
...
@@ -2,7 +2,7 @@ spack:
init
:
"
"
# command to load spack environment, e.g. module load spack,
# use spack/setup-env.sh if empty
url
:
https://github.com/spack/spack.git
# url to download spack if necessary
branch
:
develop
# if downloaded, branch name to use
branch
:
v0.20.1
# if downloaded, branch name to use
externals
:
"
"
# list of packages we try to find with spack external find
# In LMU we need to include slurm to this list.
compiler
:
"
gcc@12.2.0"
# desired compiler for spack
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
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