Conversation
Agent-Logs-Url: https://github.com/E3SM-Project/mache/sessions/e345fcab-a62f-41fc-90bc-c49d8613faae Co-authored-by: xylar <4179064+xylar@users.noreply.github.com>
config_machines.xml to E3SM 4487cd1 and update Frontier GNU Spack externals
|
@copilot, you are making changes to Frontier files based on changes to |
Agent-Logs-Url: https://github.com/E3SM-Project/mache/sessions/2f8a3e6e-ffc2-4205-8fd9-7d6a627bbf90 Co-authored-by: xylar <4179064+xylar@users.noreply.github.com>
|
@copilot, sorry, my mistake. There were, indeed, frontier changes. Your changes now look right to me. Again, sorry. |
Good catch — those Frontier template edits were not intended to be driven by |
TestingI was able to deploy all 7 spack environments for Polaris for the 6 compilers on Frontier with these changes. |
Daily drift detected changes in supported machine config for
bebop,frontier, andimprov. This PR syncsmache/cime_machine_config/config_machines.xmlto upstream E3SM revision4487cd1c5daf8ab1de910a9d0c74be4b8e813bfband updates the affected FrontierSpack templates for module/version drift.
config_machines.xmlupstream syncmache/cime_machine_config/config_machines.xmlwith generatedupstream content from E3SM
4487cd1c5daf8ab1de910a9d0c74be4b8e813bfb.upstream_config_machines.xmlfrom the repo root.Frontier Spack template alignment
mache/spack/templates/frontier_craygnu_mpich.yamlmache/spack/templates/frontier_craygnu-mphipcc_mpich.yamlFrontier drift in the synced machine configuration:
cpe/24.11→cpe/25.09gcc-native/12.3→gcc-native/14.2hdf5 1.14.3.3→1.14.3.7netcdf-c 4.9.0.15→4.9.2.1parallel-netcdf 1.12.3.15→1.12.3.19prefix:paths keepgnu/12.3(notgnu/14.2) for these externals.drift, not on
cruxmachine settings.Checklist
Testingcomment, if appropriate, in the PR documents testing used to verify the changesFixes #407