-
Notifications
You must be signed in to change notification settings - Fork 250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cleanup CCPP cmake build, reduce number of compile jobs, use atparse for variable substitution in MOM and CICE input files #791
Conversation
Automated RT Failure Notification |
Automated RT Failure Notification |
Automated RT Failure Notification |
Cheyenne tests failed due to disk quota issues (presumably), I cleared the scratch area, will add labels for GNU and Intel one after the other. Gaea: Will rerun failed tests manually. |
Except for orion, all regression tests finished and were successful. On Orion, we still have several jobs in the queue. |
All tests on orion passed so far, one remaining one is still running. I am going to start merging ccpp-framework and ccpp-physics. |
…hub.com/climbfuji/ufs-weather-model into ccpp_cmake_cleanup_speedup_compile_jobs
I verified hash for fv3atm to be correct (85c2648). |
PR Checklist
Ths PR is up-to-date with the top of all sub-component repositories except for those sub-components which are the subject of this PR. Please consult the ufs-weather-model wiki if you are unsure how to do this.
This PR has been tested using a branch which is up-to-date with the top of all sub-component repositories except for those sub-components which are the subject of this PR
An Issue describing the work contained in this PR has been created either in the subcomponent(s) or in the ufs-weather-model. The Issue should be created in the repository that is most relevant to the changes in contained in the PR. The Issue and the dependent sub-component PR
are specified below.
[n/a] If new or updated input data is required by this PR, it is clearly stated in the text of the PR.
Description
-DCCPP_SUITES
argument to the extent that the Intel compilers allow it (i.e. do not abort with internal compiler errors)Issue(s) addressed
Testing
How were these changes tested? What compilers / HPCs was it tested with? Are the changes covered by regression tests? (If not, why? Do new tests need to be added?) Have regression tests and unit tests (utests) been run? On which platforms and with which compilers? (Note that unit tests can only be run on tier-1 platforms)
Dependencies
Associated PRs: