Skip to content

Test Spack CI Fix For spack-config#31

Closed
CodeGat wants to merge 4 commits into
releases/v1.1from
test-v1.1-ci-updates
Closed

Test Spack CI Fix For spack-config#31
CodeGat wants to merge 4 commits into
releases/v1.1from
test-v1.1-ci-updates

Conversation

@CodeGat
Copy link
Copy Markdown
Member

@CodeGat CodeGat commented Apr 9, 2026

  • include.yaml: redirect to ACCESS-NRI's spack-config
  • ci: Clone spack config in prechecks

harshula and others added 2 commits April 8, 2026 16:07
* Spack CI needs access to spack-config, so clone it in theDockerfile.
@CodeGat CodeGat force-pushed the test-v1.1-ci-updates branch from 87134b3 to 61c6624 Compare April 9, 2026 01:58
@CodeGat
Copy link
Copy Markdown
Member Author

CodeGat commented Apr 9, 2026

Okay, this might be a bit more complex than I first thought...the CI creates users and there are permissions issues when cloning our access-spack-packages repo as a sibling of spack

@CodeGat CodeGat closed this Apr 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants