2022-06 spack update #949
Labels
Comments
|
|
our genten needs updates due to kokkos API changes - wait for new higher order moments branch to be merged into genten master. |
I am seeing repeated fetch errors for sphinx source from spack mirrors. |
I also hit consistent errors with spack fetching python (both 3.8 and 3.9) I disabled python to get a minimal container - but we need python to generate the unit test reports we rely on in CI. So CI tests fail with this container. |
|
Python 3.9 built with newer spack, however hit an activation error: Same error in Python 3.8. More details: Both the main python install: And the setup tools install: contain this
I tried two older versions of pysetup tools I am not sure if this is an issue with spack environment views. @white238 saw this spack issue in another project. I created a spack issue with a simple recipe to reproduce: |
Hitting an issue bootstrapping clingo on Ubunutu 22.04 with gcc. Here we are trying |
VTK-m Cuda build is failing in ubuntu 18.04 cuda 11.4 container builds: The spack build process hangs before it cleans up, the hang is due to some lock in use by spack. I hunted around and found the logs while the spack process was still hung. Kokkos build errors. I need to explicitly disable kokkos in VTK-m (it was on for another package, not VTK-m) |
Device Link Errors with Dray + Umpire. |
mfem failed to build in cuda container. problem with petsc, which comes in directly from mfem and also sundials, new mfem spec for cuda container: |
Umpire config issue in cuda container: |
They got moved from ascent/src/cmake/thirdparty/SetupUmpire.cmake Lines 12 to 14 in 1641fc7 |
|
@white238 thanks this also explains an issue I had building dray release with spack. |
now umpire can't find camp, I might have to explicitly set camp dir? Answer: Yes |
Current CUDA Spack TPL install size comparisons: Old: 3.5GB Issue: System cuda is not being used, spack is installing cuda 11.7 , config was not being passed to uberenv due to typo in script. |
Now we have RAJA BLT issue: |
|
problem using ubernev + spack on macos: concertize can't figure out what to use for If I try to disable ownlibs, I get another problem: uberenv-ascent inheriting from ascent seems to be completely confusing the clingo concretization process: ==> Error: No valid value for variant 'ownlibs' of package 'cmake' |
|
the issue is related to disabling local configs: when we don't disable, it works. Still working on root cause, we are not using |
|
To update this thread: We hit issues with rocm package layouts vs what the spack packages expected. For hip builds, we are using a script. |
|
Since we are tracking spack develop (which was an accident on my part), I hit an issue with macOS not being able to build openmpi. Consistently fails to fetch hwloc source. spack/spack#32503 Also raja tries to build with openmp support, but we don't have in default macOS compilers -- so we have to use |
|
Related PR #1012 |
|
Spack was updated for CI part of the VTK-m 1.9 update - #1015. We still do not have a method for using spack for hip builds, instead we use build_ascent_hip.sh` and friends. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using this issue to track all steps for to update to latest Spack for our CI builds and deployment on ECP platforms.
Changes needed to existing dependent packages on spack develop:
Missing Public Packages:
Ascent Public (spack develop) Package Changes:
Ascent hot-copy (uberenv) Package Changes:
CI Container Config and Build Updates
ECP Public Install Config and Build Updates:
The text was updated successfully, but these errors were encountered: