-
Notifications
You must be signed in to change notification settings - Fork 81
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
Fix CI #741
Fix CI #741
Conversation
Locally it's failing for me with scipy 1.14 but not with previous ones. Checking that in CI now. |
And now it seems that https://github.com/choderalab/openmmtools/actions/runs/10424368899/job/28873034656#step:6:64 |
Related issue #661 |
f409b03
to
5238e58
Compare
Do we want to support windows? I am also not sure if this is a "real" error or not, but IMHO we should have an except for
|
I'd vote for making windows support not required. As in, we can make the windows CI job optional. |
More importantly, I think we are not running a big chunk of the tests when changing to pytest. Locally I'm getting the following:
I'm not sure EDITED: I ran pytest with |
Hmm, good question. I don't know if by making it catch the |
I've seen this before, I think it has to do with not doing a dev install |
I ran the tests locally and this is what I'm getting for coverage reports. It seems fine as far as I can tell. (
|
Oh, nvm, I do see a difference in testing the |
…tes a system we need, also want to add to the existing cases and not get rid of the othe ones
slow tests running here: https://github.com/choderalab/openmmtools/actions/runs/10568140366/job/29278645522 |
Slow tests passed! It took 3.5 hours, so ~$1.82 per run |
@mikemhenry nice! We would need to separate the ruff/black/formatter changes in a separate commit, that way it's going to be way easier for me to review, and hopefully also ignore those so that we don't change the blame, which I think it's important to maintain. |
@ijpulidos when we merge this in, it will be squashed into a single commit we can add it to
I will see if I can rebase things that way |
Or maybe it would be better to squash everything into two commits, automated refactor and non-automated, and only add the auotmated refactor commit to |
Yes, that would definitely make the review easier. Considering it's such a big set of changes otherwise, I would just review the non-automated commit. |
I will get this rebased into a few smaller commits, I don't think I can get it into two, but I will tag + link the non-automated commits when it is ready |
Okay I've rebased a few commits on a different branch (If I made a mistake I didn't want to wreck all of my work). Once you are good with it, I will add a Commits to review: Commits to add to |
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.
This is great! Finally we can move to a modern unit testing infrastructure and GPU CI. There are just minor non-blocking comments.
I think we have talked about how nose
counts tests differently compared to pytest
and that the coverage information should account for this. We want to make sure we are doing as good or better in terms of coverage.
Great work! LGTM!
@@ -18,15 +18,14 @@ dependencies: | |||
- python | |||
- python | |||
- pyyaml | |||
- scipy | |||
- scipy <1.14 |
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.
Non-blocking comment. Why is it that we are not supporting scipy 1.14+? I wonder if we then have to restrict the version on the conda-forge package and also patch/change all the currently released packages so that older versions don't get installed when environment with scipy 1.14 are resolved. I hope that makes sense.
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 will relax the pin and see if we have any issues, I am pretty sure it was actually something to do with nose testing or a numba thing
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.
Yes, that should be a quick test, great!
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.
Oh, I think it was probably related to this, which should've been already fixed on the openmm side. But if we are supporting older OpenMM releases then we might still need the pin. #743
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.
we will need the pin until this gets merged in conda-forge/openmm-feedstock#139 + we patch the older releases
Update to PyTest (Rebased Edition) See #741
Done in #746 |
Description
Provide a brief description of the PR's purpose here.
Todos
Status
Changelog message