-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
MRG, MNT: Migrate to nbclient for notebook testing #7944
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
MRG, MNT: Migrate to nbclient for notebook testing #7944
Conversation
|
Now there is a warning on Azure for notebook testing: |
|
Bumping |
|
I think it's fine since |
|
This is trickier than it seems. There is an API change in |
|
As we do not gather coverage informations from this notebook testing, I could consider migrating to |
|
I reported the For now, we can just pin |
|
What do you think @agramfort, @larsoner ? |
|
I am confused. Why removing pytest-notebook? |
|
We don't use the coverage information and it's not ready yet for |
|
What do you mean we don't use it? It should be reported like all other runs (other than style) |
I was not aware of that |
|
coverage report or execution? I can live without coverage but the notebook
definitely needs to be
executed by pytest
… |
|
I'm now completely lost for coverage. |
|
if test.ipynb runs on CIs than I am happy
… |
As long as it does this in the same Python process, I think https://codecov.io/gh/mne-tools/mne-python/src/master/mne/viz/backends/_notebook.py |
|
Closing in favor of #7943 |

Checks that the CIs are green on Azure for the notebook 3d backend.