Use spack's 1.0 release branch and separate spack-packages repo in CI - #1311
Conversation
|
cscs-ci run |
|
cscs-ci run |
msimberg
changed the title
|
cscs-ci run |
|
cscs-ci run |
1 similar comment
|
cscs-ci run |
|
cscs-ci run |
|
cscs-ci run |
|
cscs-ci run |
|
cscs-ci run |
|
cscs-ci run |
1 similar comment
|
cscs-ci run |
|
cscs-ci run |
|
cscs-ci run |
|
cscs-ci run |
|
cscs-ci run |
|
cscs-ci run |
|
@rasolca when you have time, do you have ideas about what might be happening with the coverage reports on eiger? The creation of the reports times out on all the test jobs on eiger with 1, 4, 16, 32 threads... so I suspect it has nothing to do with the number of threads anymore. |
Please disable coverage. Might be the same issue I observed on GH. Priority is having CI running. We can check coverage later. |
|
Opened #1337 to track reenabling CI. |
| SPACK_SHA: develop-2025-02-09 | ||
| SPACK_SHA: fbadf557433ae3d8cb8a2b63a81303de42a9fd6f | ||
| SPACK_PACKAGES_SHA: bf71e784ba28818a05468ce4ffef405fa7c3d151 | ||
| ALPS_CLUSTER_CONFIG_SHA: 3c26eb25bdfa3151b637c040154a55bb9da31ba1 |
There was a problem hiding this comment.
Note that this is eth-cscs/alps-cluster-config@3c26eb2, i.e. not a commit on alps-cluster-config main. @simonpintarelli is looking at making a similar on main. Once that's in we could go back to a non-custom commit.
|
cscs-ci run |
RMeli
left a comment
RMeli
left a comment
There was a problem hiding this comment.
LGTM. I already applied the same changes to DLA-Future-Fortran in eth-cscs/DLA-Future-Fortran#46.
|
cscs-ci run |
|
I disabled the GCC 13 codecov pipeline. All pipelines are now passing. |
4 participants
No description provided.