-
Notifications
You must be signed in to change notification settings - Fork 34
Trying to speed up CI a little bit #1131
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
base: main
Are you sure you want to change the base?
Changes from all commits
04af8ab
59d3336
642096c
a005cab
8027511
72b99f3
73c199f
4e0b907
967f01a
0cc968e
ab46a8a
fff615b
9dbe310
4d98877
4137d16
1cbc2a4
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -230,8 +230,9 @@ def get_settings(): | |
|
|
||
| class TestFEAnalysis: | ||
|
|
||
| # Note: class scope _will_ cause this to segfault - the reporter has to close | ||
| @pytest.fixture(scope='function') | ||
| # Note: scope on this can sometimes cause segfault, may need to revert to | ||
| # function scope if it happens. | ||
| @pytest.fixture(scope='class') | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. this is purely for speed-up reasons? I'm hesitant about increasing test fixture scope as a shortcut if we're at all concerned about them being mutated.
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. (for the future) we discussed this and agreed that we should remove session scopes on everything. |
||
| def reporter(self): | ||
| with resources.as_file(resources.files('openfe.tests.data.openmm_rfe')) as d: | ||
| ncfile = str(d / 'vacuum_nocoord.nc') | ||
|
|
@@ -247,7 +248,7 @@ def reporter(self): | |
| finally: | ||
| r.close() | ||
|
|
||
| @pytest.fixture() | ||
| @pytest.fixture(scope='class') | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. same question as above
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. (for the future) this one really benefits from a session scope, we'll try to leave it here for now. |
||
| def analyzer(self, reporter): | ||
| return multistate_analysis.MultistateEquilFEAnalysis( | ||
| reporter, sampling_method='repex', | ||
|
|
||
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.
Is it pre-charging the molecule that does the speed-up here? If so, can we just include the charges hard-coded in the file, so that we 1) don't need to generate charges at all and 2) remove any reproducibility issues stemming from the partial charge method?
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 should, but replacing benzene_modifications directly is a bit of a pain because we have tests that check for charges (or lack thereof) that uses these files. So we should do it as a separate data entry (in a separate issue).
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.
There are no reproducibility issues with gasteiger charges. They are fully reproducible, all the time.
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.
According to @jthorton it's not if the hybridization changes - so it's onlys table if rdkit doesn't change the graph