Test on last release of PyMC instead of main #125
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ricardoV94
force-pushed
the
test_last_pymc_release
branch
from
fc0427d
to
53bdcdd
Compare
|
Why does it not find pymc5.1.2? Could it be because of the defaults channel? pymc-experimental/conda-envs/windows-environment-test.yml Lines 3 to 4 in 53bdcdd CC @maresb |
ricardoV94
force-pushed
the
test_last_pymc_release
branch
from
c7110d9
to
29740d2
Compare
ricardoV94
force-pushed
the
test_last_pymc_release
branch
3 times, most recently
from
0cd802c
to
70256a8
Compare
ricardoV94
force-pushed
the
test_last_pymc_release
branch
from
70256a8
to
f31c518
Compare
Windows returns `np.float32`, which is not an instance of `float`
|
At last :D |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Otherwise it's a bit of a mess when we are changing API across releases
We might even undo changes before a release, and we shouldn't be patching the code here until it becomes "fixed".
Related to #124
Closes #123