Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recreate symlinks from spack-config to $spack/etc/spack after force checkout #44

Open
CodeGat opened this issue Mar 28, 2024 · 1 comment

Comments

@CodeGat
Copy link
Contributor

CodeGat commented Mar 28, 2024

See failed run: https://github.com/ACCESS-NRI/ACCESS-OM2/actions/runs/8447128060/job/23136977611#step:6:125
We hadn't deployed in a while, so ACCESS-NRI/spack-config@3317dd2 went under the radar. When we deployed, there were a bunch of broken symlinks, so we couldn't find the spack-packages install, and then couldn't find the access-om2 package.

We should make deployment update the symlinks after we have done a git checkout --force of spack-config.
Essentially:

rm <all the broken symlinks>
ln -s -r -v spack-config/v0.20/gadi/* spack/etc/spack/
@CodeGat
Copy link
Contributor Author

CodeGat commented May 7, 2024

Although this might not be an issue if ACCESS-NRI/spack-config#30 is merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant