-
Notifications
You must be signed in to change notification settings - Fork 12
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
Investigate path forward for SDK conda build #131
Comments
I agree that we should aim for an exaworks conda package. |
Ozgur @okilic1 will start to look into this issue
|
@okilic1 what is the status on this? |
This is on my to-do list. I will start working on that next week. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The SDK container builds with conda are no longer working. The build was only successful in a small subset of the build matrix anyways, so a new approach might be more successful. What would it take to add an
exaworks
conda package? Is this a better path forward? In this case, we could add bare metal tests to the conda environment in addition to the Spack environment. This issue should track progress on what best path forward would be and what steps need to be taken.The text was updated successfully, but these errors were encountered: