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

feature #1566 Use Python 3.8.6 for automated tests #1710

Merged
merged 26 commits into from
Jul 26, 2022

Conversation

georgemccabe
Copy link
Collaborator

@georgemccabe georgemccabe commented Jul 25, 2022

Pull Request Testing

  • Describe testing already performed for these changes:

Created new Docker images with Conda environments named ending with .v5 that uses Python 3.8.6 instead of Python 3.6.
Ran all use case tests

  • Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:

Confirm that any differences in use cases you are familiar with are expected (we have already discussed these)

  • Do these changes include sufficient documentation updates, ensuring that no errors or warnings exist in the build of the documentation? [Yes]

Updated instructions to create Conda environments and updated comments in each script to create each env to include the version numbers of the packages that were installed.

  • Do these changes include sufficient testing updates? [Yes]

  • Will this PR result in changes to the test suite? [Yes]

Some small differences were flagged in a few use cases. These are due to slightly differences due to using a different version of some of the Python packages, such as rounding differences and different default size of images

  • Please complete this pull request review by 7/29/2022.

Pull Request Checklist

See the METplus Workflow for details.

  • Add any new Python packages to the METplus Components Python Requirements table.
  • Review the source issue metadata (required labels, projects, and milestone).
  • Complete the PR definition above.
  • Ensure the PR title matches the feature or bugfix branch name.
  • Define the PR metadata, as permissions allow.
    Select: Reviewer(s)
    Select: Organization level software support Project or Repository level development cycle Project
    Select: Milestone as the version that will include these changes
  • After submitting the PR, select Linked issues with the original issue number.
  • After the PR is approved, merge your changes. If permissions do not allow this, request that the reviewer do the merge.
  • Close the linked issue and delete your feature or bugfix branch from GitHub.

…en test to see if use cases that use that env still work using the .v5 version, ci-run-all-diff
…nda environments built from Python 3.8.6, ci-run-all-diff
… be consistent in the automation logic and avoid special behavior for those environments
…ently by excluding the version number. Cleaned up logic to add version number extension to conda environment names as needed
…or METdataio (renamed from METdatadb) to use in automated tests for v5
…t is installed in the Docker Conda environments used for the automated tests to ensure that the same environment will be generated even if the default version of the package differs from the env used to create them
@georgemccabe georgemccabe added this to the METplus-5.0.0 milestone Jul 25, 2022
@georgemccabe georgemccabe linked an issue Jul 25, 2022 that may be closed by this pull request
25 tasks
@DanielAdriaansen
Copy link
Contributor

I inspected the differences in the use case "6.2.5.1. Multi_Tool: Feature Relative by Lead using Multiple User-Defined Fields" for the saturation equivalent potential temperature (sept/SEPT) field. These differences were on the order of 3e-5 K, which I consider to be extremely small. I approve.

@georgemccabe
Copy link
Collaborator Author

@CPKalb confirmed with me that the changes to the s2s output as acceptable. The images that were generated from the use case are a slightly different size, but the content on the graphs are the same. Merging PR and updating truth data in develop-ref.

@georgemccabe georgemccabe merged commit 45da99e into develop Jul 26, 2022
@georgemccabe georgemccabe deleted the feature_1566_python_3.8.6 branch July 26, 2022 17:48
georgemccabe added a commit that referenced this pull request Jul 26, 2022
Co-authored-by: George McCabe <23407799+georgemccabe@users.noreply.github.com>
Co-authored-by: Mrinal Biswas <biswas@ucar.edu>
Co-authored-by: Hank Fisher <fisherh@kiowa.rap.ucar.edu>
Co-authored-by: Minna Win <minnawin@kiowa.rap.ucar.edu>
Co-authored-by: bikegeek <3753118+bikegeek@users.noreply.github.com>
Co-authored-by: Christina Kalb <kalb@kiowa.rap.ucar.edu>
Co-authored-by: Julie Prestopnik <jpresto@seneca.rap.ucar.edu>
Co-authored-by: johnhg <johnhg@ucar.edu>
Co-authored-by: Hank Fisher <fisherh@seneca.rap.ucar.edu>
Co-authored-by: Mrinal Biswas <biswas@seneca.rap.ucar.edu>
Co-authored-by: jprestop <jpresto@ucar.edu>
Co-authored-by: j-opatz <jopatz@ucar.edu>
Co-authored-by: Kathryn Newman <knewman@seneca.rap.ucar.edu>
Co-authored-by: j-opatz <59586397+j-opatz@users.noreply.github.com>
Co-authored-by: Lisa Goodrich <lisag@ucar.edu>
Co-authored-by: Julie Prestopnik <jpresto@ucar.edu>
Co-authored-by: Christina Kalb <kalb@mohawk.rap.ucar.edu>
Co-authored-by: bikegeek <minnawin@ucar.edu>
Co-authored-by: Hank Fisher <fisherh@ucar.edu>
Co-authored-by: Christina Kalb <kalb@ucar.edu>
Co-authored-by: lisagoodrich <33230218+lisagoodrich@users.noreply.github.com>
Co-authored-by: Howard Soh <hsoh@seneca.rap.ucar.edu>
Co-authored-by: Molly Smith <molly.b.smith@noaa.gov>
Co-authored-by: hsoh-u <hsoh@ucar.edu>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

Update Python requirement to 3.8.6
2 participants