-
Notifications
You must be signed in to change notification settings - Fork 24
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
Add a new workflow for concretization and delete older concretization workflows #646
Conversation
git clone https://github.com/spack/spack -q | ||
source spack/share/spack/setup-env.sh |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This could be a
- uses: actions/checkout@v4
with:
repo: spack/spack
path: spack
at the top. Potentially, even ref: $(cat ${GITHUB_WORKSPACE}/.latest-commit)
works, but since we need the history of develop
as well, we would then also have to tweak the fetch-depth
, so I am not sure whether it's worth it to specify that here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I'm not sure. The checkout action seems to do more things and sometimes it takes more than a simple clone.
I'll merge this so it can be used for other PRs even though the issue described in github.com/orgs/community/discussions/63579 is happening. |
This workflow will run concretization on alma9 and ubuntu22 with the environments that are used for the release and nightly builds. They have the issue shown in https://github.com/orgs/community/discussions/63579 but I think it's good enough.