Closed hagrid67 closed 9 months ago
I've commented out the if false
in checks.yml
so that tox -e notebooks now runs.
I've fixed most of the notebooks listed so the task completes successfully.
The notebook test_service.ipynb
needs a redis
server - raising a separate issue for this.
Objectives
Let's enable the notebooks in
checks.yml
. If there are problem notebooks, these can be removed fromtox.ini
which any of us can change.I have now made this change using a GitHub personal access token, "classic" style, with workflow permission.
Todos comment out / remove
if: ${{ false }}
in checks.yml notebooks section.Minimal testing requirements none - this change will enable some notebooks to be run as a test.
Additional context This change forms part of #39 - Include running notebooks in CI.
run-all-notebooks.py
did once run a list of working notebooks, by forking / execing a separate process runningnbconvert
for each notebook. It used a filenotebook-list
to list which notebooks were eligible for running. The intention was at least partly to check for changes which broke the notebooks; however the mechanism was removed from the build / CI some time ago (back in gitlab days). The approach was ad hoc and obsolete and we now have thepytest
pluginnbmake
.I've added the list of notebooks to tox.ini
testenv:notebooks
and it works locally withtox -e notebooks
The notebook
test-service.ipynb
needsredis
-- this runs an evaluator process in the background and a client in the foreground. It's a bit contrived / "heath robinson" but I gather @manuschn Manuel would like us to do some evaluator work so it may be worthwhile, if this is simple to enable on github. If not then remove this notebook from the list intox.ini
.