-
Notifications
You must be signed in to change notification settings - Fork 172
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
Run one executable for soca2cice (instead of two) #3118
Run one executable for soca2cice (instead of two) #3118
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @shlyaeva !
@WalterKolczynski-NOAA , the GDASApp hash has been updated. This PR is ready for CI testing and review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Approve.
Since automated CI is not working for me, launch the following CI cases under my username on Hera
|
Hera g-w CI results
All DA streams successfully completed except Job gdas_aeroanlgenb failed. GDASApp issue #1381 has been opened to report this failure and document its resolution. |
GDASApp PR #1382 commented out the section of GDASApp @CoryMartin-NOAA commented
Update |
b116bf8
Experiment C96C48_hybatmDA FAILED on Hera in Build# 3 in |
Experiment C96C48_ufs_hybatmDA FAILED on Hera in Build# 3 in |
CI Failed on Hera in Build# 3
|
Ignore the failure, I'm fighting Jenkins this afternoon. |
Build FAILED on Hera in Build# 4 with error logs:
Follow link here to view the contents of the above file(s): (link) |
@WalterKolczynski-NOAA : Where do we go from here? I repeated my build of this PR on Hera in
I do not know the intricacies of Jenkins but it seems to have frequent hiccups when running g-w CI. What can we do to make Jenkins based CI more robust? I have greater success manually running
successfully ran for this PR via this approach. The following CI cases remain to be run on Hera
I assume we do not need to run the GEFS CI cases for this PR
I went ahead and manually set up C48_ATM and C48_S2SW for this PR. Both streams are now running on Hera via cron. Assuming these two streams pass, is their success along with success of the other five streams sufficient to allow this PR to be merged into Does g-w CI need to be run on other platforms? |
C48_ATM and C48_S2SW are complete.
All jobs in both streams successfully ran to completion |
Here g-w CI
|
CI Passed on Hera in Build# 5
|
Automated CI passed on Hera. Yeah! |
@WalterKolczynski-NOAA : Is the Hera success sufficient? If not, on what other machines should I run? |
1ba8985
into
NOAA-EMC:develop
Thank you @WalterKolczynski-NOAA ! |
Thank you all so much for very quick reviews, testing and turnaround! |
Description
Run a single executable to add soca increments to cice restart files, processing arctic and antarctic simultaneously to save on runtime and I/O.
Resolves NOAA-EMC/GDASApp#1367
Type of change
Change characteristics
How has this been tested?
Checklist