-
Notifications
You must be signed in to change notification settings - Fork 9
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
Use Sage 2.2.0 RC1 as default #307
Conversation
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.
Thanks @mattwthompson it would be great to make this change!
No idea why the OpenEye integration tests are failing ... |
Oh no looks like some strange interaction with fitting on top of this force field. We did see an error like this before but that was fixed by using the new geometric #243. |
Any other ideas where to start? The main thing that stands out to me is the toolkit difference, but I doubt that either
|
I don't know how to isolate this behavior locally, and there have been some other quiet issues bumping OpenEye Toolkits from 2022 to 2023, so I'm just going to constrain down to what we know worked before |
@jthorton Any other ideas? Matt and I just looked at this and are stumped. It looks like we're using the latest geometric too. |
A more useful error:
|
6a879be
to
0e1d23f
Compare
I don't think we should merge this in a form where a RC is the default FF. It's fine if we use it as part of the debugging process but we shouldn't put an RC into production. |
Right, but this should be ready to go on release |
Well this is very confusing as the new RC passes all the tests. |
Won't work until conda-forge/openff-forcefields-feedstock#25 is through |
The new FF package should be available now. Fixed a little typo and kicked CI. |
This has one approving review, which is fairly old but in the spirit of its current state. Everything is green, so I'm merging |
#306