Repository navigation
Updating towards mpich 4.2.2 images - #11
Merged
Merged
Conversation
|
Looks fine to me. |
ddeeptimahanti
approved these changes
Oct 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
openfoam/container.yamlnow only lists the images for this openfoam flavour with mpich 4.2.2 that are going to be deployed:No versions are to be deprecated for this flavour in Setonix.
The
openfoam-org/container.yamlnow only lists the images for this openfoam flavour with mpich 4.2.2 that are going to be deployed:Versions 8 & 9 for this flavour are being deprecated in Setonix.
Images are already pushed in quay and their hash can be checked from there.
The installation of the SHPC modules is not tested here (as installation of OpenFOAM modules in Setonix take a very complicated series of steps in the installation scripts living in the
pawsey-spack-configrepository. Therefore, thetest_install_shpc_openfoam.shis created and run from that other repository. The check here is just a reading-check of the files updated here.main files to check are the two
container.yamlfiles, that the SHA hashes match witht those in quay, and that the aliases files exist (check of the content of the aliases files is not necesssary)