-
Notifications
You must be signed in to change notification settings - Fork 47
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
Feature/ami tier2 update 1.9 #1516
base: release/1.9.0
Are you sure you want to change the base?
Feature/ami tier2 update 1.9 #1516
Conversation
…into feature/ami_tier2_update_1.9
…into feature/ami_tier2_update_1.9
…into feature/ami_tier2_update_1.9
@@ -202,7 +204,7 @@ exit | |||
```bash | |||
# if in sudo su - | |||
cd /opt | |||
git clone -b develop --recursive https://github.com/jcsda/spack-stack.git | |||
git clone -b release/1.9.0 --recursive https://github.com/jcsda/spack-stack.git |
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 README.md will eventually be merged back into develop. I assume you want this to be reverted when that happens? How do we keep track of this?
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.
I can change these now, actually. I was thinking about it, and really the doc update was me making sure I didn't miss a step. I'll change these back to develop since I have instances ready for the release.
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.
@climbfuji I've reverted it back to develop, so we should be good with a merge.
Co-authored-by: Dom Heinzeller <[email protected]>
Co-authored-by: Dom Heinzeller <[email protected]>
I'm testing this branch on my EC2 Ubuntu 24.04 instance. The current state of this feature branch enables concretize to work out of the box which is great! I'm currently running spack install. I'll keep you posted. |
The install failed on numactl. I'm seeing this error in the configure step:
I can't get to this again until tomorrow (sorry). In the meantime, do you have any thoughts about what might be causing this? Thanks! |
Any feedback on the build error that @srherbener reported? |
I haven't been able to reproduce it. I'll keep trying this morning and hopefully have an update soon! |
I have sync'd up my local clone on my EC2 instance (about 20 minutes ago) and am trying the build over from scratch. The concretize step worked out of the box, and the install is running now. I'll keep you posted. |
If @stiggy87 can't reproduce the error, the issue might be that my instance is missing something that @stiggy87 had to install or upgrade (external to spack-stack) to get the spack-stack build working. I launched my instance about a month ago, and we have been trying to keep it up to date (but who knows?). I would be inclined to abandon testing my instance if @stiggy87's works (call the PR good), build the AMI from his instance, and I can destroy my instance and relaunch it from the new AMI. |
Found the issue, the |
I'll try adding libtool to my instance, and retry the build. I'm not clear if anyone has done the build from scratch yet, so I've changed my mind and thought it would be good for me to try again. Thanks! |
Summary
Updated configs for tier2 AWS AMI.
Testing
Built and tested both
gcc
andoneapi
usingunified-dev
.Pulled jedi-bundle, built, and ran ctest.
Systems affected
AWS
Checklist