Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Our automated check against new OpenMM release candidates picked up a new RC last night, and the build is failing with a conda
UnsatifiableError
. I'm going to try to fix this on our side. Among other things, it seems like there's a weird combination trying to pull inpython=3.10
while also pulling inpypy3.6
, which seems like an obvious source of conflict. We don't currently test against 3.10, so I'm guessing that's the issue (this fails before we try to install the OpenMM RC, so I suspect the problem due to changes in the GitHub Actions environment, not due to the RC itself).I'll do a little on this now, but if my first tries don't solve, I'll come back to it later in the day (after 19:00 GMT).
The offending conda command in line 17 in the "Install requirements" stage: