Raise the execution timeout to 30 minutes for the CPU-only runners - #156
Merged
Conversation
numpy_vs_numba_vs_jax stopped fitting the 600s cell timeout on ubuntu-latest: five consecutive cache builds timed out on it on 2026-08-18. cache.yml builds without -W so those runs stayed green while leaving the notebook out of .jupyter_cache, which is what made the publish-2026aug19 publish (-W) fail. The English repo keeps 600s on its GPU runners. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
✅ Deploy Preview for majestic-griffin-10b166 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR increases the notebook execution timeout in the Jupyter Book configuration so the numpy_vs_numba_vs_jax benchmark lecture can complete on CPU-only GitHub Actions runners without timing out during cache/publish workflows.
Changes:
- Increased
execute.timeoutfrom 600 seconds to 1800 seconds (30 minutes). - Updated the inline comment to document why the higher timeout is needed for this repository’s CPU-only runners.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
numpy_vs_numba_vs_jaxbenchmark lecture no longer completes inside the 600 s cell timeout on this repo'subuntu-latest(CPU-only) runners: five consecutive cache builds timed out on it on 2026-08-18. Becausecache.ymlbuilds without-W(the translation-era TODO), those runs stayed green while leaving the notebook out of.jupyter_cache— which is exactly why thepublish-2026aug19publish, which does use-W, then had to execute it and failed (run 32195426355). The English repo keeps 600 s because its builds run on GPU runners; this repo executes the benchmark on shared CPU, where it is borderline by design, so the ceiling moves to 30 minutes.Merging this triggers
cache.ymlon main (push trigger), which rebuilds the cache under the new ceiling; once that cache is complete, the failedpublish-2026aug19run can simply be re-run — the tag already points at the right commit, and with a complete restored cache the-Wbuild has nothing left to execute.Mirrors the identical change in QuantEcon/lecture-python-programming.fr#36.
🤖 Generated with Claude Code