-
Notifications
You must be signed in to change notification settings - Fork 11
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
Change clifford to run with pytest #28
Conversation
We've dropped our nose dependency in clifford, and moved away from unittest-compatible tests in order to use pytest fixtures. The upshot is our tests should be more granular.
There are still some |
No, that hasn't been released yet. Do these tests run against both master and the released version, or only the released version? If the former, I could revert my removal of |
These tests usually only run against the latest released version. |
For clifford specifically, the program will obtain all git tags from the 'blessed' remote and select the 'latest' one. The code is here: https://github.com/numba/numba-integration-testing/blob/master/switchboard.py#L115 |
It sounds then like the correct action is to leave this open until clifford pushes its next tag? |
@eric-wieser probably, yes. |
Clifford did a 1.1.0 release, although now I expect this to fail due to a missing |
@eric-wieser thanks for submitting this, I'll try to re-run this PR now. |
@eric-wieser for reference, you can add a string like |
I think the clifford tests are going through fine, but that is because
|
Co-Authored-By: Valentin Haenel <esc@users.noreply.github.com>
@eric-wieser thanks for submitting a fix for this, will merge as soon as CI goes green! |
It looks like it has passed, but actually I see:
|
Looks like we may have to wait for: conda/conda#9665 |
I have merged a workaround for the |
^ That should have the effect of re-running against master |
@eric-wieser yeah, I thought so too, but apparently CircleCI doesn't seem to operate like that. |
I triggered it manually now. |
Test failure is real, Looks like the numba API changed on us. |
@eric-wieser indeed, we are in the middle of a 'refactor the world' update in Numba: numba/numba#5197 It is very likely that this broke clifford and lead to the failures you are seeing now. I would suggest to collect all the places where the Numba refactor broke clifford and submit these in an issue for discussion on the Numba issue tracker. This will allow us to decide if we broke a 'public' API and we need to fix Numba --- OR --- if clifford was using a private API in the first place and the fix needs to happen there. And thanks very much for your continued understanding, patience and persistence --- we appreciate it! |
At any rate, this PR should be good to merge, right? |
@eric-wieser indeed! The errors are being reported again and the clifford tests no longer fail due to a missing |
We've dropped our nose dependency in clifford, and moved away from unittest-compatible tests in order to use pytest fixtures. Since python 2 is also not supported, the
future
module is no longer a dependency.The upshot is our tests should be more granular.