Repository navigation
build(fates): Add dynamic HLM_ROOT configuration for standalone FATES builds - #1605
Draft
johnpaulalex wants to merge 2 commits into
Draft
johnpaulalex wants to merge 2 commits into
johnpaulalex wants to merge 2 commits into
Conversation
Contributor
|
@johnpaulalex was this test on |
Contributor
Author
|
Hey @glemieux , I didn't run any tests, but I marked b4b because it's just choosing the right paths to do the compilation. Is that misleading? |
Contributor
@johnpaulalex it's not misleading because its under the "expectation ..." heading. I just wanted to double check since I thought I remembered you getting access to derecho. |
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.
Description:
This change enhances CMake configuration and Python test suite path resolution to support building and testing FATES in standalone repository setups.
HLM_ROOTpath determination inCMakeLists.txtand CIME path resolution intesting/framework/utils/path.pynow support an optionalHLM_ROOTenvironment variable, falling back gracefully to the standard nested directory layout.This allows both development scenarios:
HLM_ROOTenvironment variable to point to the host model / CTSM installation directory.HLM_ROOT(the default fallback path logic automatically locates the host model / CIME directory relative to the FATES root).Specific notes
Collaborators:
Parent PR (if stacked on a parent branch):
Linked issues addressed, if any:
Expectation of Answer Changes:
Description of generative AI usage (as necessary)
Google Antigravity was used to write the code and tests, followed by human-guided verification.
Checklist
Contributor
Integrator
Test Results:
CTSM (or) E3SM (specify which) test hash-tag: N/A
CTSM (or) E3SM (specify which) baseline hash-tag: N/A
FATES baseline hash-tag:
093b4f46Test Output:
[x] Executed pFUnit / CIME regression tests