-
Notifications
You must be signed in to change notification settings - Fork 86
Fix toolkit tests #227
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 toolkit tests #227
Conversation
|
The Python 3.8 failure is cryptic but the 3.10 failures look "correct" to me, and they fail in 10 minutes compared to 30-40, which implies to me OpenEye Toolkits are actually being used |
|
Supersedes #225 |
|
I'm looking to find a more stable and portable way to ship the XML files. I can't for the life of me figure out why the symlinks are going two directories up? It looks like these paths are in the root of the repo. Lines 24 to 26 in d4e6a07
|
|
I do think the root of a lot of issues is not packing data files correctly, we should probably switch to a modern approach |
|
The thing is, I'm pretty sure the package data is configured properly, or at least uses an approach that's on the better end of current best practices: Lines 59 to 73 in d4e6a07
Exactly why symlinks should be used is not clear to me; they're not portable and it saves no space on disk. I've attempted to remove them altogether with #229 |
Add boilerplate `.gitignore` file
Do not pull from non-standard labels
Install instead of update
Try to figure out why if: {{ false }} still triggers
Syntax?
Tinker
Bring in (full) mamba
Bash thing everywhere
Bring down old toolkit
Do not present un-loadable ff14SB port as available
More pins
|
After excessive and inefficient iterations on my part, I think this is ready for review. It includes at least the following changes:
There's more I'd like to do, but this is already borderline unreviewable due to my lack of restraint. I can't do much more than point to that the automation has been improved and tests are passing. |
|
I can't request a review via the UI since you opened it, so a ping will have to do @mikemhenry |
mattwthompson
left a comment
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 approve (I think?)
|
I'll review this PR after lunch to just double check it, but it should be good to merge in, like we don't have others we want to merge in first, right? @mattwthompson |
|
Nope, the other PRs have either been merged into this one or were experiments that didn't work out. It's just this one (for now)! |
| - name: CodeCov | ||
| if: ${{ github.repository == 'openmm/openmmforcefields' | ||
| && github.event != 'schedule' }} | ||
| - name: Upload coverage report to CodeCov |
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 add a quick guard to not upload coverage reports when it is scheduled CI
|
@mattwthompson I will take over from here! I just have a few things I want to tweak before I get it merged in, again, thanks for all your help! |
|
Great!!! Thank you! |
No description provided.