Submodule update
Updates application submodules
Job VTB Documentation, step Sync Docs on e359014 wanted to post the following:
View the site here
This comment will be updated on new commits.
@pbehne are they all HPC-deployed submodules?
@pbehne are they all HPC-deployed submodules?
Yes, everything except SAM and relap:
Looking for hpc submodule versions
- Found hpc sha 8f19da0 for submodule bison
- Found hpc sha 2a81957 for submodule griffin
- Found hpc sha 6e89be5 for submodule pronghorn
- Could not determine hpc version for SAM. Falling back to default behavior.
- Found hpc sha 0870433 for submodule sockeye
- Found hpc sha dea0472 for submodule direwolf
- Found hpc sha e4d0168 for submodule bluecrab
- Found hpc sha 2e1ad10 for submodule cardinal
- Could not determine hpc version for relap-7. Falling back to default behavior.
- Found hpc sha e1e49ae for submodule moose
- Found hpc sha f07d3a0 for submodule mastodon
Checking out branch 'submodule_update'
Resetting submodule_update in /data/behnpa/projects/virtual_test_bed to latest upstream/devel
Updating submodules
- apps/bison to 8f19da0
- apps/griffin to 2a81957
- apps/pronghorn to 6e89be5
- apps/SAM to origin/master
- apps/sockeye to 0870433
- apps/dire_wolf to dea0472
- apps/blue_crab to e4d0168
- apps/cardinal to 2e1ad10
- apps/relap-7 to origin/master
- apps/moose to e1e49ae
- apps/mastodon to f07d3a0
Here are the available bison modules on hpc:
[behnpa@rod ~]$ module spider bison
-----------------------------------------------------------------------------------------------------------------------
bison-coupletest-openmpi:
-----------------------------------------------------------------------------------------------------------------------
Versions:
bison-coupletest-openmpi/2024.09.27-a169ad1
bison-coupletest-openmpi/2024.10.12-31e8faf
-----------------------------------------------------------------------------------------------------------------------
For detailed information about a specific "bison-coupletest-openmpi" package (including how to load the modules) use the module's full name.
Note that names that have a trailing (E) are extensions provided by other modules.
For example:
$ module spider bison-coupletest-openmpi/2024.10.12-31e8faf
-----------------------------------------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------------------------------------
bison-openmpi:
-----------------------------------------------------------------------------------------------------------------------
Versions:
bison-openmpi/2024.08.22-37928d0
bison-openmpi/2025.03.13-618b661
bison-openmpi/2025.03.31-cf80d8a
bison-openmpi/2025.04.12-5ae1f05
bison-openmpi/2025.04.29-41f37ba
bison-openmpi/2025.05.12-ce069ab
bison-openmpi/2025.05.30-f47516a
bison-openmpi/2025.06.14-4a0d04d
bison-openmpi/2025.06.19-f718b8e
bison-openmpi/2025.06.30-e7afde6
bison-openmpi/2025.07.14-a87760a
bison-openmpi/2025.07.30-8eed390
bison-openmpi/2025.08.14-8f19da0
bison-openmpi/2025.08.27-feec5cf
bison-openmpi/2025.08.30-6a97bce
bison-openmpi/2025.09.12-b33bb7c
-----------------------------------------------------------------------------------------------------------------------
For detailed information about a specific "bison-openmpi" package (including how to load the modules) use the module's full name.
Note that names that have a trailing (E) are extensions provided by other modules.
For example:
$ module spider bison-openmpi/2025.09.12-b33bb7c
-----------------------------------------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------------------------------------
bison-openmpi-cudatorch:
-----------------------------------------------------------------------------------------------------------------------
Versions:
bison-openmpi-cudatorch/2025.03.13-618b661
bison-openmpi-cudatorch/2025.03.31-cf80d8a
bison-openmpi-cudatorch/2025.04.12-5ae1f05
bison-openmpi-cudatorch/2025.04.29-41f37ba
bison-openmpi-cudatorch/2025.05.12-ce069ab
bison-openmpi-cudatorch/2025.05.30-f47516a
bison-openmpi-cudatorch/2025.06.14-4a0d04d
-----------------------------------------------------------------------------------------------------------------------
For detailed information about a specific "bison-openmpi-cudatorch" package (including how to load the modules) use the module's full name.
Note that names that have a trailing (E) are extensions provided by other modules.
For example:
$ module spider bison-openmpi-cudatorch/2025.06.14-4a0d04d
-----------------------------------------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------------------------------------
bison-squashfs-openmpi: bison-squashfs-openmpi/2025.08.14-8f19da0
-----------------------------------------------------------------------------------------------------------------------
Right now, the submodule updater script takes the hash from the last entry. In this case, it gets 8f19da0 from bison-squashfs-openmpi: bison-squashfs-openmpi/2025.08.14-8f19da0. Is this the version we want to be using?
This one
bison-openmpi/2025.09.12-b33bb7c
is probably the better one
Okay, I updated the submodule update script to look for openmpi packages only. I also fixed the issue where it was checking for module spider SAM instead of module spider sam. I don't see any modules for relap on hpc. If this goes well, I'll make a separate PR for the script updates.
looks like we need to skip a hpmr_h2 tests with BC new diff with relap7 new error i think with DW?
The failures in the Blue Crab HPC recipe will self-resolve one the blue crab submodule is updated to a version containing griffin commit https://github.inl.gov/ncrc/griffin/commit/6a953f1e5653aed9035d763e750edaacb82a45b9.
All other failures seem unrelated to me.