-
Notifications
You must be signed in to change notification settings - Fork 65
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
update uberenv and related configs #1164
Conversation
First all around successful set of builds, but new spack times are much slower:
Some of this is b/c we are using less system libs. We had to exclude:
I think the big one we are missing is lapack. That said, even the minimal build is 120% of our prior setup. Docker builds are timing out on circle CI (circle ci max time is 1 hour, for ref docker build takes 74 minutes now on github actions) |
external lapack pulls us back from the edge of the cliff for circle ci. |
Blocking Issue: Much like Uberenv can do this, however even though it looks like sphinx was built -- I don't see it in the generated spack env view. |
Spack deps tagged as Will see if there is an option to include the, if not I will drop |
We can add py-sphinx to the env to have it available in the view. However, when we do so - the main package concretizes with Talked to Todd Gamblin, the concretizer is making a strange choice. I decided the simplest solution is to remove the |
sphinx 7.0.0 fails to build docs. seems like an input config file change. |
Newer spack:
Looks the same as spack/spack#39538, however our tests aren't running on arm processors. mpi4py fails to build on m1 mac
|
need more path adjustments |
C++ 17 tests are failing often due to MPI related errors. Not sure if there are real issues, or if this is a setup and tear down MPI issue related to multiple MPI tests.
|
No description provided.