Skip to content
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

gdaspostanl should report failure if files do not show up before job ends #520

Closed
WalterKolczynski-NOAA opened this issue Dec 7, 2021 · 11 comments
Labels
bug Something isn't working

Comments

@WalterKolczynski-NOAA
Copy link
Contributor

If the loop waiting for output files to show up exhausts all iterations before files are available, the job should register as failed, not succeeded.

One GDAS cycle (2020083018) has several analysis files missing. There was a failure in the gdasanalcalc step, but upon rerun it completed successfully. However, the gdaspostanl step timed out in the meantime and skipped processing the analysis. There was no failure recorded for this task:

@WalterKolczynski-NOAA
Copy link
Contributor Author

@lgannoaa please submit it as a PR to the post repo

@lgannoaa
Copy link
Contributor

lgannoaa commented Feb 9, 2022

Created issue 443 in UPP because script in question exgdas_atmos_nceppost.sh and exgfs_atmos_nceppost.sh is belong to UPP repo.

@lgannoaa
Copy link
Contributor

UPP CM has merged my fix PR. Close this issue.

@WalterKolczynski-NOAA
Copy link
Contributor Author

This needs to stay open until we update our post version in the checkout script.

@lgannoaa
Copy link
Contributor

lgannoaa commented May 3, 2022

@WenMeng-NOAA , there is a PR #444 that addressed this issue. Looks like you merged that in. The Global Workflow develop currently checkout upp_v10.0.11. This version does not contain this fix. Would you please provide us another UPP version that included this fix for us to checkout?
Thanks
Lin

@WenMeng-NOAA
Copy link
Contributor

@lgannoaa I assume you are meaning the UPP PR #444. You may checkout the latest UPP develop branch revision 5f60e60.

@WalterKolczynski-NOAA
Copy link
Contributor Author

I'm using the current UPP develop in moving all the scripts to global-workflow (Issue #769), so this issue will be fixed by that as well.

@WenMeng-NOAA
Copy link
Contributor

@WalterKolczynski-NOAA Before you take further actions of moving out all gfs post processing scripts from UPP repository to global-workflow, some coordination efforts are needed between managements of VPB and EIB, like GFS product user support, GFS post processing operation support handoff. @HuiyaChuang-NOAA may chime in.

@HuiyaChuang-NOAA
Copy link

@WalterKolczynski-NOAA @arunchawla-NOAA

Hi, Walter, I just spoke to Arun. We're supportive of EIB taking over GFS post processing scripts but given Wen is pretty busy and also her first check indicated your new scripts have inadvertently removed existing operational GFS products, I would
like to propose the followings going forward:

  1. we will not remove any post processing scripts from UPP repository until EIB takes over all post processing scripts and both post processing team and EIB verify all operational capabilities are being replicated by EIB's new post processing scripts.
  2. with that said, please proceed to transition all gfs post processing scripts to EIB workflow and when you've completed all transition, please reach out to us, and we will check the final scripts and products.

Again, I recommend that we try to replicate operational GFS post processing capabilities first. Thank you. I will also send this as an email to a bigger group.

@WalterKolczynski-NOAA
Copy link
Contributor Author

@HuiyaChuang-NOAA @WenMeng-NOAA we should probably move this conversation over to Issue #769. The matter was only incidentally mentioned here.

@WalterKolczynski-NOAA
Copy link
Contributor Author

When we moved all the UPP scripts into workflow, we updated to the tip of the UPP develop, so this issue should be satisfied.

kayeekayee pushed a commit to kayeekayee/global-workflow that referenced this issue May 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants