Fix JAX warnings in tests #307
Merged
Conversation
This file contains hidden or 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
jessegrabowski
force-pushed
the
fix-tests2
branch
from
6996b4b to
23a1c1c
Compare
jessegrabowski
force-pushed
the
fix-tests2
branch
from
a0cd7ef to
9f19dda
Compare
|
I wanted to filter by module ( By far my worst work, but it fixes it issue. I'd still like to move |
ricardoV94
approved these changes
Feb 12, 2024
Let's do that in a separate PR |
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.
Closes #305
JAX warning mentioned #305 seems to be caused by using multiple cores when sampling with pm.sample in tests. The JAX test appears to be over-eager, because it is issued even when JAX is not being used, as long as JAX has been imported.
This PR adds the warning to
filterwarningsin thepyproject.toml, since it doesn't appear to be relevant to the tests its causing to fail.