Use develop branches for repositories in ufs bundle#30
Conversation
…ndle into feature/use_develop
climbfuji
left a comment
climbfuji
left a comment
There was a problem hiding this comment.
This all works for me, I can compile UFS_APPs ATM, ATMAERO, NG-GODAS, S2S. The ATM ctests (warmstart) pass, the coldstart tests fail as expected.
shlyaeva
left a comment
shlyaeva
left a comment
There was a problem hiding this comment.
Looks good to me, and as @climbfuji suggested, would be great to have CI on this now that it uses develop for most branches in the bundle (otherwise it may be hard to find which changes will be breaking it eventually).
| module load jedi-ufs-env/skylab-dev | ||
| module load jedi-ufs-env/unified-dev | ||
| ``` | ||
| Further, for testing of the newest `fms@2023.02-beta1` tag, verify if the platform you are on has this version available and if yes, run |
There was a problem hiding this comment.
Does this include the change that soca needed?
There was a problem hiding this comment.
🎉 you rock!
we'll test with fv3-jedi too, unless @travissluka you already tested with both soca and fv3-jedi?
There was a problem hiding this comment.
Well, the tag of fms contains the changes that SOCA needs, but the ufs-weather-model, fv3-jedi-linearmodel and fv3-jedi don't work with that tag ye. See ufs-community/ccpp-physics#90 and https://github.com/JCSDA-internal/fv3-jedi-linearmodel/issues/18 for examples. Also, see NOAA-GFDL/FMS#1284 for bugs in the build system of that tag.
There was a problem hiding this comment.
Got it, so testing https://github.com/JCSDA-internal/fv3-bundle/pull/103 (with updates to jcsda repos) isn't expected to work?
There was a problem hiding this comment.
At least at the moment, not. Let's see how far we get this week.
3 participants
Description
Fixes #29
Working on develop would be easier to maintain (for me, at least!)
Goes with: