CellTimeoutError after a cell runs for 30 seconds

[MaxGhenis]

Describe the bug

After upgrading to 0.8.0, I started getting a notice saying (about index.ipynb):

Did not execute index. Set jupyter_execute_notebooks to force to execute

Even though the cell outputs are in the locally-executed notebook, they don't show up in the website.

After setting execute_notebooks: 'force', I instead got this warning:

WARNING: Execution Failed with traceback saved in /home/runner/work/childallowance/childallowance/jb/_build/html/reports/index.log

That log file said:

nbclient.exceptions.CellTimeoutError: A cell timed out while it was being executed, after 30 seconds.

Pages built from the notebook again don't show outputs.

Per jupyter/nbconvert#256 it looks like this setting can be changed in nbconvert itself, but did something change in 0.8.0 around this behavior? If making that change in nbconvert is the solution, could you share how I should go about it?

Environment

• Python Version [e.g. 3.7.1]: 3.7.7
• Package versions or output of jupyter-book --version:
  Jupyter Book: 0.8.0
  MyST-NB: 0.10.0
  Sphinx Book Theme: 0.0.36
  MyST-Parser: 0.12.8
  Jupyter-Cache: 0.4.1
  NbClient: 0.4.0
• Operating System: Chrome OS/Ubuntu

[chrisjsewell]

Heya, @MaxGhenis perhaps you missed the section on execution timeouts 😉 ? https://jupyterbook.org/content/execute.html#setting-execution-timeout

Also note nbconvert is not used for execution, which is essentially deprecated for nbclient

[chrisjsewell]

I would also personally recommend using execute_notebooks: 'cache', which is the more sophisticated option for documentation rebuilds. In fact really I would like to deprecate auto, but that's another issue lol (#947)

[MaxGhenis]

Thanks, passing -1 looks like it kept the execution time running, my bad not searching the docs. Outputs still aren't showing up but I might have to investigate that separately.

[chrisjsewell]

No worries thanks, I guess I'll close this, in place of the more specific #948