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

Add deployment tests workflow #207

Merged
merged 32 commits into from
Nov 25, 2024
Merged

Add deployment tests workflow #207

merged 32 commits into from
Nov 25, 2024

Conversation

mattwthompson
Copy link
Member

@mattwthompson mattwthompson commented Dec 15, 2022

Description

This PR adds deployment tests ("conda tests")

Status

  • Ready to go

@mattwthompson

This comment was marked as outdated.

@codecov
Copy link

codecov bot commented Dec 20, 2022

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.24%. Comparing base (d5a46df) to head (ae78156).
Report is 33 commits behind head on main.

Additional details and impacted files

@mattwthompson mattwthompson force-pushed the add-deployment-action branch from 07bb689 to 0ab00b3 Compare January 4, 2023 21:30
@mattwthompson

This comment was marked as off-topic.

@mattwthompson

This comment was marked as outdated.

@mattwthompson
Copy link
Member Author

@mattwthompson mattwthompson force-pushed the add-deployment-action branch from 899a5d6 to 0cd73f0 Compare January 6, 2023 16:17
@mattwthompson

This comment was marked as outdated.

@mattwthompson
Copy link
Member Author

@Yoshanuikabundi
Copy link
Contributor

Hey @mattwthompson, sorry I'm only just now getting around to this. I have no idea what's going on here - the test passes locally with the new deployment environment, and I'm just seeing what happens when I try the entire test suite now. I don't even know what test_get_molecule_image does. If everything passes locally I'll see if I can just skip the crashing test, as it looks like there are other failures - maybe they'll shine some light on what's going on.

It looks like the 0.2.0 release is broken - #213 - which was apparently not detected by tests. I think we need some full on integration tests where we try to run an entire fit - the current unit tests don't seem to cut it. So these deployment tests are definitely important and good!

@jthorton
Copy link
Contributor

jthorton commented Jan 9, 2023

| I think we need some full on integration tests where we try to run an entire fit

Yes I think we do it looks like this test should have picked up on the forcebalance incompatibility but has been mocked probably to try and reduce the CI time but I think its more important that its tested?

@Yoshanuikabundi
Copy link
Contributor

Another test is crashing now - I wonder if the problem is that the CI environment is headless? Both crashing tests have "image" in the name. But not sure why tests would pass in regular CI but not here.

@jthorton
Copy link
Contributor

jthorton commented Jan 9, 2023

I think it was an openeye license issue. I saw this in the log that failed LICENSE: No product keys!

# This is the 1st commit message:

Add deployment tests

# This is the commit message #2:

Update

# This is the commit message #3:

Fix

# This is the commit message #4:

Trim down differences between environments

# This is the commit message #5:

Try to isolate crash

# This is the commit message #6:

Rename environment

# This is the commit message #7:

Further pare down environments

# This is the commit message #8:

Bump Python version

# This is the commit message #9:

Update environments

# This is the commit message #10:

Double check OpenEye license
Update

Fix

Trim down differences between environments

Try to isolate crash

Rename environment

Further pare down environments

Bump Python version

Update environments

Double check OpenEye license

Skip crashing test
author Matthew W. Thompson <mattwthompson@protonmail.com> 1673977806 -0600
committer Matthew W. Thompson <mattwthompson@protonmail.com> 1673977819 -0600

Add deployment tests

Update

Fix

Trim down differences between environments

Try to isolate crash

Rename environment

Further pare down environments

Bump Python version

Update environments

Double check OpenEye license

Skip crashing test

Skip another crashing test

Tinker with OpenEye config

Update Psi4 installation instructions

Assume version 0.1.3
@mattwthompson

This comment was marked as outdated.

@Yoshanuikabundi
Copy link
Contributor

Thanks Matt - Looks like the geometric issues were fixed in #243 by pinning Geometric=1. Now that 0.2.1 is out, I've updated this to use it - and things seem to be working!

@mattwthompson mattwthompson reopened this Nov 14, 2024
@mattwthompson mattwthompson marked this pull request as ready for review November 14, 2024 15:51
Copy link
Member

@j-wags j-wags left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good @mattwthompson, just trying out some polishes. Will approve+merge once I see if these work, so nothing more needed from you. Thanks!

devtools/conda-envs/deployment.yaml Outdated Show resolved Hide resolved
.github/workflows/deployment.yaml Outdated Show resolved Hide resolved
devtools/conda-envs/deployment_openeye.yaml Outdated Show resolved Hide resolved
devtools/conda-envs/docs-env.yaml Outdated Show resolved Hide resolved
@j-wags j-wags merged commit 3802c15 into main Nov 25, 2024
11 checks passed
@j-wags j-wags deleted the add-deployment-action branch November 25, 2024 19:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants