-
Notifications
You must be signed in to change notification settings - Fork 1
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 specs for conduit tests #10
base: master
Are you sure you want to change the base?
Conversation
@cyrush For the duration of your PR, you should change |
Right now, it triggered a pipeline for the |
A few notes: The system configs (packages.yaml) are based off of @davidbeckingsale's - however they are not exactly the same b/c: I need to test building conduit's python support -- and since it extends python, spack has to build python as part of the process. |
One way we could "uniformize" this would be to agree on a limit for things to share, and things that should be in the project spack.yaml:
Then the questions is: what about small utilities (m4, pkg-config, and such)? |
That’s because we can have two source for the |
Note: clingo compiler takes ages, that’s what we are looking for at the moment. |
this is where my head starts to spin - I feel like we get into a scenario where we need scripts to combine (override, union) shared packages. Solving this in a nice way would make sharing all of these things much much easier. |
If only we knew the nice way :) |
Does spack configs allow this kind of "overriding" with multiple environments? A bit like how you can have repos that override packages... |
@davidbeckingsale my impression is that we can override part of the configs directly in the spack.yaml:
I don't know if there is such a thing as stackable environments. All I know is that environment modularity is currently being revisited by @becker33 |
@cyrush I hope the lassen jobs are producing useful input (there was a failure of one conduit spec). In the meantime, I am trying to decrypt the "KeyError" on quartz. |
Believe it on not but it looks like just today there were 2 changes in spack@develop that "alter" things in our pipelines. |
No description provided.