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

Upgrade to spack-stack 1.6.0 #884

Closed
DavidHuber-NOAA opened this issue Jan 3, 2024 · 4 comments
Closed

Upgrade to spack-stack 1.6.0 #884

DavidHuber-NOAA opened this issue Jan 3, 2024 · 4 comments
Assignees
Labels

Comments

@DavidHuber-NOAA
Copy link
Collaborator

DavidHuber-NOAA commented Jan 3, 2024

UFS_Utils should be upgraded to use the newest suite of spack-stack libraries (version 1.6.0). This includes an upgrade of CRTM to 2.4.0.1, netcdf-fortran to 4.6.1, and prod_util to 2.1.1. This has already been tested successfully on Hercules on a test build of spack-stack, though official installations have not yet been rolled out.

@DavidHuber-NOAA
Copy link
Collaborator Author

@GeorgeGayno-NOAA The c96_viirs.bnu grid_gen test is failing on Jet with the error

forrtl: severe (28): CLOSE error, unit 15, file "Unknown"

when the program is stopped at line 165 of mtnlm7_oclsm.F. Looking through the code, I do not see any point where unit 15 is opened, though it is read at line 598. This seems like a bug, though Hera and Orion ran the test successfully. Is this a known issue?

@GeorgeGayno-NOAA
Copy link
Collaborator

@GeorgeGayno-NOAA The c96_viirs.bnu grid_gen test is failing on Jet with the error

forrtl: severe (28): CLOSE error, unit 15, file "Unknown"

when the program is stopped at line 165 of mtnlm7_oclsm.F. Looking through the code, I do not see any point where unit 15 is opened, though it is read at line 598. This seems like a bug, though Hera and Orion ran the test successfully. Is this a known issue?

I have not heard of the problem before. Just curious if you are you able to run the head of 'develop' on Jet successfully.

@DavidHuber-NOAA
Copy link
Collaborator Author

Running the develop branch does not produce the error. I'm going to run the spack-stack branch once more to see if this is intermittent or easily reproducible with the newest library versions.

@DavidHuber-NOAA
Copy link
Collaborator Author

Indeed, the job passed the second go around, so it seems to be intermittent. I will open an issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants