-
Notifications
You must be signed in to change notification settings - Fork 92
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
Back-porting PRs to 0.8.4 branch #856
Conversation
Co-authored-by: SimonBoothroyd <[email protected]>
Co-authored-by: SimonBoothroyd <[email protected]>
Co-authored-by: SimonBoothroyd <[email protected]>
…a will write ['canonical_isomeric_explicit_hydrogen_mapped_smiles'] in extras dict, one test included to check the roundtrip
…s will always have cmiles entry with current fix
… on line 1904, 1912 since CI tests are failing because of a different ordering even though the atoms are tagged
I have a few failing tests from the start
This was done with my current development environment with both OpenEye toolkits and The RDKit installed. I also ran without OpenEye toolkits and everything passed - effectively a false positive because of
Running with The RDKit but no OpenEye toolkits produces the same failed tests as above. The current deprecation warning seems accurate. Would it be worth it to also link to #819, here or in the release notes? __main__:1: DeprecationWarning: Importing this package as `import openforcefield.XXX` and `from openforcefield import XXX` was marked for deprecation in version `0.8.3`. From version `0.9.0` onwards this package will need to be imported as `import openff.toolkit.XXX` and `from openff.toolkit import XXX`. See the `0.8.3` release notes for more information. |
Thanks, Matt. I'm going to keep banging on this today and will ping you when it's ready for review! |
Codecov Report
|
…in molecule.smirnoff/amber_impropers
…in topology{,molecule}.smirnoff/amber_impropers
…replace openff.toolkit with openforcefield
Don't review this yet. I think there's actually a significant test failure. https://github.com/openforcefield/openff-toolkit/runs/2036523162#step:12:50065 This is code adjacent to some of our current WBO work/bugfixes. I'm not sure that it's good to keep this as xfail. https://github.com/openforcefield/openff-toolkit/blame/master/openff/toolkit/tests/test_toolkits.py#L2930 I'll debug more tomorrow. |
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.
Took a brief skim through the files and couldn't find anything objectionable. I'm restarting the tests; if the only failure is the stochastic one we've already discussed, LGTM
Good news❓ Nothing fails any more❓❓ Hooray❓❓❓ |
We're aiming to make a 0.8.4 release simultaneous with 0.9.1. If possible, these releases will be feature-equivalent.
0.8.4 will be the last release of the
openforcefield
namespace.This PR cherry picks the development that has occurred on
master
to the0.8.4-rc
branch. It's my first time doing a cherry pick of this scale, so I suspect that this will require a little polishing to get CI happy again.