-
-
Notifications
You must be signed in to change notification settings - Fork 155
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
Investigate use of numba.config.DISABLE_JIT
for coverage approximations
#1449
Comments
Looking into this I noticed that |
That sounds good! |
So it sounds like even if you use: from numba.tests.support import override_config
with override_config('DISABLE_JIT', True):
aesara_numba_fn(*inputs) So if the function has already been compiled, If so, we can probably change the cache directory dynamically, perhaps with a |
We're currently using a hackish
mock
approach to estimating coverage for our Numba implementations; however, this is cumbersome to use and extend. Let's take (another) look at the use ofnumba.config.DISABLE_JIT
for these purposes.For instance, instead of
eval_python_only
ataesara/tests/link/numba/test_basic.py
Line 241 in 404e2d4
we would—ideally—have something the following:
A change like that would need to be followed by some
pytest
runs with coverage enabled, and the results would need to indicate that coverage was obtained for the Python code produced for Numba by Aesara.The text was updated successfully, but these errors were encountered: