Add CI to compare stacks, checking for both modules and extensions#913
Conversation
|
Instance
|
|
Instance
|
|
Instance
|
|
Instance
|
|
Instance
|
|
Instance
|
|
@casparvl This highlights the remaining differences between Zen4 and the rest of the software stacks: Comparing /cvmfs/software.eessi.io/versions/2023.06/software/linux/x86_64/amd/zen4/modules/all to /cvmfs/software.eessi.io/versions/2023.06/software/linux/x86_64/generic/modules/all
{
"module_differences": {
"missing": [
"GDRCopy/2.3.1-GCCcore-12.3.0.lua",
"ipympl/0.9.3-foss-2023a.lua",
"UCX-CUDA/1.14.1-GCCcore-12.3.0-CUDA-12.1.1.lua",
"Z3/4.12.2-GCCcore-12.3.0-Python-3.11.3.lua",
"NCCL/2.18.3-GCCcore-12.3.0-CUDA-12.1.1.lua",
"OSU-Micro-Benchmarks/7.2-gompi-2023a-CUDA-12.1.1.lua",
"CUDA-Samples/12.1-GCC-12.3.0-CUDA-12.1.1.lua",
"CUDA/12.1.1.lua",
"UCC-CUDA/1.2.0-GCCcore-12.3.0-CUDA-12.1.1.lua"
],
"added": []
},
"extension_differences": [
{
"R-bundle-CRAN/2023.12-foss-2023a.lua": {
"missing": [],
"added": [
"cmna/1.0.5",
"XBRL/0.99.19.1",
"rhandsontable/0.3.8"
]
}
}
]
} |
|
Given that our plan is to remove the CUDA stuff from the CPU stacks, I could add a filter for modules containing |
Maybe. Or maybe this should be a good trigger to actually remove it... |
|
Ok, discussed with @bedroge and we'll deprecate first. See https://gitlab.com/eessi/support/-/issues/128 . So, if we want this check in CI, we'll have to make an exception at least for now for the CUDA stuff. |
|
After syncing the |
|
Maybe this should actually be moved to the docs repo? We already have a missing installations check here. This check is a bit more strict though since it also checks the extensions. |
I think it's a better fit here, since it's a check for the installations we have in the software layer? |
|
The modules have been removed, so I'm rerunning the CI of this PR. |
|
PR merged! Moved |
1 similar comment
|
PR merged! Moved |
No description provided.