Source set_strict rather than call it as a function#4690
Source set_strict rather than call it as a function#4690CoryMartin-NOAA wants to merge 7 commits intoNOAA-EMC:developfrom
Conversation
|
@RussTreadon-NOAA @DavidNew-NOAA I have a hunch this will require changes to GDASApp tests. Let me check and if so, I will open a PR there too. EDIT: A grep/search says we should (hopefully) be good |
|
Running -G and -C tests on Ursa. Will report back once they are done. |
|
All tests passed on Ursa. Ready for review and more thorough CI testing. |
DavidHuber-NOAA
left a comment
There was a problem hiding this comment.
Looks good! One thought, but not necessary to incorporate into this PR.
This reverts commit a839dc2.
|
Changes to DA monitor jobs and script look good. I think exgdas_atmos_verfozn.sh needs to be included in these changes too, doesn't it? |
|
@EdwardSafford-NOAA I didn't see the set_strict in that file |
|
Ok, just thought it might need to be included because its parent J-job is. If that's not the case then all good and I'll approve. |
Description
To adhere to NWS operational standards, we must, rather than define and execute bash functions to set and unset strict mode, source
ushscripts that set and unset strict mode. This PR removes the functions and instead creates simplified bash that can be sourced, and all places that previously called the functions have been replaced by a source of the scripts.Additionally, the set_strict has been removed from jjob_shell_setup and is now explicitly called at the top of every j-job.
Resolves ##4682
Type of change
Change characteristics
How has this been tested?
On Ursa:
Checklist