You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recently discovered an example of code in a Foundations notebook that is failing (#343). We discovered this by accident while perusing the published pages. It's not clear how long that code has been failing.
This is basically a bug in our nightly health checks. We currently use allow_errors: True in the Foundations config file, so any run-time errors are silent and do not show up as CI failures.
The reason for using allow_errors: True is because we have cells in notebooks that are supposed to fail for demonstration purposes.
But we need a better way of identify unexpected failures.
We discussed the same question for Cookbooks here: ProjectPythia/cookbook-template#53.
The consensus there was to use allow_errors: False but set raises-exception flags on cells that are expected to fail.
It's unclear if anyone has tested this and if it will play well with JupyterBook.
I think we should investigate this option for Foundations.
The text was updated successfully, but these errors were encountered:
We recently discovered an example of code in a Foundations notebook that is failing (#343). We discovered this by accident while perusing the published pages. It's not clear how long that code has been failing.
This is basically a bug in our nightly health checks. We currently use
allow_errors: True
in the Foundations config file, so any run-time errors are silent and do not show up as CI failures.The reason for using
allow_errors: True
is because we have cells in notebooks that are supposed to fail for demonstration purposes.But we need a better way of identify unexpected failures.
We discussed the same question for Cookbooks here: ProjectPythia/cookbook-template#53.
The consensus there was to use
allow_errors: False
but setraises-exception
flags on cells that are expected to fail.It's unclear if anyone has tested this and if it will play well with JupyterBook.
I think we should investigate this option for Foundations.
The text was updated successfully, but these errors were encountered: