Pin jax to 0.11.0 in CI — jax 0.11.1 hangs the fori_loop cells on CPU - #157
Merged
Conversation
jax 0.11.1 (2026-08-17) regresses lax.fori_loop on the CPU path: numpy_vs_numba_vs_jax executes in seconds under 0.11.0 and exceeds even the new 1800s cell timeout under 0.11.1. This repo had no workflow-level jax install, so the lecture's unpinned '!pip install quantecon jax' cell resolved the broken release on every build. Full evidence and the family-wide exposure map are recorded in QuantEcon/workspace-lectures#49. 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
Pins JAX in the GitHub Actions build workflows to avoid a regression in lax.fori_loop CPU execution that causes the numpy_vs_numba_vs_jax lecture to hang during automated builds/publishing.
Changes:
- Add an explicit CI-time
pip install "jax==0.11.0"step in the PR (ci), cache build, and publish workflows. - Document (in workflow comments) why the pin exists and where the supporting evidence is recorded.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| .github/workflows/ci.yml | Installs pinned JAX before building the lecture site in PR CI to prevent fori_loop CPU hangs. |
| .github/workflows/cache.yml | Installs pinned JAX before the cache build to ensure cached executed outputs don’t pick up the regressed version. |
| .github/workflows/publish.yml | Installs pinned JAX before publish builds so tag-based releases don’t hang during execution. |
💡 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.
jax/jaxlib 0.11.1 (released 2026-08-17 20:31 UTC) regresses
lax.fori_loopon the CPU execution path:numpy_vs_numba_vs_jaxexecutes in seconds under 0.11.0 and exceeds even an 1800 s cell timeout under 0.11.1 (locally bisected — the same jitted fori_loop hangs with and without the deprecateddevice=cpuargument). This repo had no workflow-level jax install at all, so the lecture pip cell resolved the broken release on every build — this is what failed the publish-2026aug19 run twice, at both 600 s and 1800 s ceilings. After merge, the on-push cache rebuild should finally carry the executed lecture, and the failed publish run can be re-run.The full evidence chain, family exposure map, and the unpin condition are recorded in QuantEcon/workspace-lectures#49. One PR per repo with this same change; with jax pre-installed, the lecture's unpinned
!pip install quantecon jaxcell is satisfied and does not upgrade.🤖 Generated with Claude Code