-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Add backports module and backport logp syntax #5083
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
Conversation
The compilation error in that test appeared on another PR a few days ago already. |
@@ -13,6 +13,7 @@ jobs: | |||
floatx: [float32, float64] | |||
test-subset: | |||
- | | |||
--ignore=pymc3/tests/test_backports.py |
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.
Just curious why do we need to ignore it here? is it due to CI 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.
The first job in this matrix is the fall-back which runs all test files that aren't explicitly mentioned by the others.
It's complemented by the check_all_tests_are_covered.py
pre-commit script checking that there's also no test file that's run by another job but not ignored here.
Pro-tip: On main
you can run python scripts/check_all_tests_are_covered.py
locally and it shows you which OS/floatX combination each test file is running in.
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.
Assuming CI failures are unrelated per comment
Co-authored-by: Ravin Kumar <ravinsdrive@gmail.com>
Thank you @michaelosthege |
I did not backport the other related functions (e.g. logcdf), but the backport of
pm.logp()
alone should cover >90 % of the use cases.Closes #5052