-
Notifications
You must be signed in to change notification settings - Fork 312
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
Bfb merge tag dev166 #2334
Bfb merge tag dev166 #2334
Conversation
…rge_tag_2315_et_al
…tion' into bfb_merge_tag_2315_et_al slevis resolved conflicts: src/main/clm_driver.F90
…m' into bfb_merge_tag_2315_et_al
…rge_tag_2315_et_al
…ge_tag_2315_et_al
Submitting test-suites first, then will prep the ChangeLog. Python tests: make all OK, pylint gives long list of warnings, which is expected and there's an open issue about that. |
For the record, I received an email titled |
That's #2213. That probably will just be a message we'll start to see. It also might mean we need to adjust it so that it's triggered less often. So it is good to know... |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
@adrifoster this is the error I see in the cesm.log of test
@adrifoster and I agreed that I will revert #2124 out of this PR and test again. |
@samsrabin on izumi Submitting the test manually This seems related to #2326 so I need your feedback on whether there a simple fix or I should back 2326 out and try again. |
@slevis-lmwg depending on how you revert #2124 here will make a difference in how we need to handle #2124. If you use git revert it will autoclose #2124 even though it's not really in. In that case we'll need @adrifoster to create a new branch and PR to keep as an outstanding draft. If you don't use git revert we should meet to talk about the trickier options. This is also something that we should decide how to handle and document it so that anyone can follow the recipe. |
@slevis-lmwg I don't think this is being caused by #2326. Could you try |
I'm getting the same error you saw with ctsm5.1.dev164 and 165. So it's not caused by #2326, but it's also not fixed by it either… |
If I add the following to my
I suggest doing that for now; I'll file an issue about how I think this should be permanently fixed. |
Thank you @samsrabin |
Thanks @ekluzek. I had already git reverted when you posted this, so I will proceed with #2334 as is and @adrifoster will likely need to replace #2124 with a new PR. Yes, we should agree on the group's accepted approach going fwd. |
Test-suites OK |
Description of changes
Simple BFB merge tag:
#2315 @TeaganKing Refactoring run_neon for PLUMBER2 part1
#2326 @samsrabin run_sys_tests: Check Python environment for FatesColdTwoStream tests
#2213 @samsrabin Automatically assign high priority items to project 25
#2330 @samsrabin Add Izumi version of the aux_clm unit testing
#2124 REMOVED due to failing tests
Specific notes
Contributors other than yourself, if any:
@TeaganKing @samsrabin @ekluzek
CTSM Issues Fixed (include github issue #):
Fixes #2315
Fixes #2326
Fixes #2213
Fixes #2330
Are answers expected to change (and if so in what way)?
No
Any User Interface Changes (namelist or namelist defaults changes)?
Testing performed, if any:
#2315 "make all" testing passes for slevis-lmwg other than long list of pylint warnings (EXPECTED)
#2124 REMOVED due to failing tests (derecho and izumi test-suites)