-
Notifications
You must be signed in to change notification settings - Fork 26
Feature 3119 installation files #3138
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
Conversation
…nstallation_files
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.
I approve of these changes. I scanned the changes major issues jumped out. Of course, the v12.1.0-rc1.tar.gz
tarfile does not actually exist yet but it will be created for the MET-12.1.0-rc1 release on/around May 21st.
I note the following details:
- The testing workflow flagged no diffs.
- The SonarQube workflow flagged no issues.
- The Python version is increased by 3.10 to 3.12.
- Increase from BUFRLIB version 11.5.0 to 11.6.0 on Acorn.
- On Acorn, link to WCOSS libraries on
dev
rather thanprod
. - New Python 3.12 miniconda environments on Casper, Hera, Jet, and Orion.
- Increase from Intel OneAPI version 2022.2.1 to 2024.1.0 on Jet and Orion.
- Casper, Hera, Jet:
Thank you for your review and for detailing those changes, @JohnHalleyGotway. I wish I had thought to do that initially in this PR. I'll try to remember that for the future. |
Expected Differences
Do these changes introduce new tools, command line arguments, or configuration file options? [No]
If yes, please describe:
Do these changes modify the structure of existing or add new output data types (e.g. statistic line types or NetCDF variables)? [No]
If yes, please describe:
Pull Request Testing
Describe testing already performed for these changes:
The files that have been updated have been tested in the installations on the various machines (except for a minor change for the upcoming rc1 installation on WCOSS2, which will be tested after the rc1 release).
Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:
Review the files for any obvious errors and ensure all tests pass. I plan to leave the issue open for further work after this is merged in.
Do these changes include sufficient documentation updates, ensuring that no errors or warnings exist in the build of the documentation? [Yes]
Do these changes include sufficient testing updates? [Yes]
Will this PR result in changes to the MET test suite? [No]
If yes, describe the new output and/or changes to the existing output:
Will this PR result in changes to existing METplus Use Cases? [No]
If yes, create a new Update Truth METplus issue to describe them.
Do these changes introduce new SonarQube findings? [No]
If yes, please describe:
Please complete this pull request review by [20250502].
Pull Request Checklist
See the METplus Workflow for details.
Select: Reviewer(s) and Development issue
Select: Milestone as the version that will include these changes
Select: METplus-X.Y Support project for bugfix releases or MET-X.Y Development project for the next coordinated release