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
lecture-python.myst · quantecon — cancelled after 120m (timed out, or the run was superseded)
lecture-python.myst · quantecon-build — cancelled after 120m (timed out, or the run was superseded)
Nobody was watching this run, so this issue is the alert. The run log shows what broke, and any job that uploads artifacts has attached its build output and failure reports to the run.
Close this issue once the workflow is green again — the next failure opens a fresh one.
lecture-python.myst · quantecon-build — cancelled after 120m (timed out, or the run was superseded)
lecture-python.myst · quantecon — cancelled after 120m (timed out, or the run was superseded)
Nobody was watching this run, so this issue is the alert. The run log shows what broke, and any job that uploads artifacts has attached its build output and failure reports to the run.
Close this issue once the workflow is green again — the next failure opens a fresh one.
lecture-python.myst · quantecon-build — cancelled after 120m (timed out, or the run was superseded)
Nobody was watching this run, so this issue is the alert. The run log shows what broke, and any job that uploads artifacts has attached its build output and failure reports to the run.
Close this issue once the workflow is green again — the next failure opens a fresh one.
lecture-python.myst · quantecon-build — cancelled after 120m (timed out, or the run was superseded)
Nobody was watching this run, so this issue is the alert. The run log shows what broke, and any job that uploads artifacts has attached its build output and failure reports to the run.
Close this issue once the workflow is green again — the next failure opens a fresh one.
lecture-python.myst · quantecon — cancelled after 107m (timed out, or the run was superseded)
lecture-python.myst · quantecon-build — cancelled after 106m (timed out, or the run was superseded)
Nobody was watching this run, so this issue is the alert. The run log shows what broke, and any job that uploads artifacts has attached its build output and failure reports to the run.
Close this issue once the workflow is green again — the next failure opens a fresh one.
lecture-python.myst · quantecon-build — cancelled after 120m (timed out, or the run was superseded)
lecture-python-intro · quantecon-build — failure after 12m
lecture-python.myst · quantecon — failure after 95m
Nobody was watching this run, so this issue is the alert. The run log shows what broke, and any job that uploads artifacts has attached its build output and failure reports to the run.
Close this issue once the workflow is green again — the next failure opens a fresh one.
lecture-python.myst · quantecon-build — cancelled after 120m (timed out, or the run was superseded)
lecture-python.myst · quantecon — failure after 77m
Nobody was watching this run, so this issue is the alert. The run log shows what broke, and any job that uploads artifacts has attached its build output and failure reports to the run.
Close this issue once the workflow is green again — the next failure opens a fresh one.
lecture-python-intro · quantecon — failure after 23m
lecture-python-advanced.myst · quantecon-build — cancelled after 25m (timed out, or the run was superseded)
lecture-python.myst · quantecon — cancelled after 25m (timed out, or the run was superseded)
lecture-python-advanced.myst · quantecon — cancelled after 25m (timed out, or the run was superseded)
lecture-python-intro · quantecon-build — cancelled after 2m (timed out, or the run was superseded)
lecture-python.myst · quantecon-build — cancelled after 25m (timed out, or the run was superseded)
Nobody was watching this run, so this issue is the alert. The run log shows what broke, and any job that uploads artifacts has attached its build output and failure reports to the run.
Close this issue once the workflow is green again — the next failure opens a fresh one.
lecture-python-intro · quantecon-build — cancelled after 7m (timed out, or the run was superseded)
lecture-python.myst · quantecon-build — cancelled after 7m (timed out, or the run was superseded)
lecture-python-advanced.myst · quantecon — cancelled after 7m (timed out, or the run was superseded)
lecture-python-advanced.myst · quantecon-build — cancelled after 7m (timed out, or the run was superseded)
lecture-python.myst · quantecon — cancelled after 7m (timed out, or the run was superseded)
lecture-python-intro · quantecon — cancelled after 7m (timed out, or the run was superseded)
Nobody was watching this run, so this issue is the alert. The run log shows what broke, and any job that uploads artifacts has attached its build output and failure reports to the run.
Close this issue once the workflow is green again — the next failure opens a fresh one.
lecture-python.myst · quantecon — cancelled after 29m (timed out, or the run was superseded)
lecture-python-advanced.myst · quantecon-build — cancelled after 29m (timed out, or the run was superseded)
lecture-python-advanced.myst · quantecon — cancelled after 28m (timed out, or the run was superseded)
lecture-python.myst · quantecon-build — cancelled after 28m (timed out, or the run was superseded)
lecture-python-intro · quantecon-build — cancelled after 14m (timed out, or the run was superseded)
Nobody was watching this run, so this issue is the alert. The run log shows what broke, and any job that uploads artifacts has attached its build output and failure reports to the run.
Close this issue once the workflow is green again — the next failure opens a fresh one.
lecture-python.myst · quantecon — failure after 118m
lecture-python.myst · quantecon-build — failure after 95m
Nobody was watching this run, so this issue is the alert. The run log shows what broke, and any job that uploads artifacts has attached its build output and failure reports to the run.
Close this issue once the workflow is green again — the next failure opens a fresh one.
lecture-python.myst · quantecon — failure after 74m
lecture-python.myst · quantecon-build — failure after 119m
Nobody was watching this run, so this issue is the alert. The run log shows what broke, and any job that uploads artifacts has attached its build output and failure reports to the run.
Close this issue once the workflow is green again — the next failure opens a fresh one.
Triage note, 2026-09-24. The latest run (35963034770, on 64aeb2f) is red for two separate reasons:
A real lecture failure. Both lecture-python.myst legs fail "Build HTML" with a CellExecutionError in lectures/bayes_nonconj.md. That is lecture content; no issue tracks it yet, and it belongs in QuantEcon/lecture-python.myst.
The work to make this matrix trustworthy is now tracked by the Project #188 (#102, #141, #142). This alert stays unparented and should close once a run is green.
Why this has been red since 2026-09-18. Two problems in lecture-python.myst cause it. Neither is in QuantEcon/actions or its images.
bayes_nonconj fails since numpyro 0.22.0 (PyPI, 2026-09-18 08:51Z), which the lecture installs unpinned (!pip install numpyro jax arviz, bayes_nonconj.md:24). 0.22.0 validates distribution arguments by default. The truncated log-normal prior (truncated_lognormal(), bayes_nonconj.md:333-336) is an ExpTransform of a TruncatedNormal(high=0). Its declared support is Positive rather than (0, 1], so NUTS initialisation can propose θ > 1, and dist.Binomial now raises.
The HTML build's CPU time sits at the job's 120-minute timeout-minutes, so whether a leg passes depends on the runner it lands on.
Tested repos, each on quantecon and quantecon-build: lecture-python-intro, lecture-python.myst, lecture-python-advanced.myst. lecture-jax is commented out.
Evidence
The switch from pass to fail matches the upload. In run 35316939330, bayes_nonconj passed at 07:05Z, before the upload (105510635506). It failed at 09:02Z, after it (105510635773). The lecture file has not changed since June. Every run since has failed it, on both images, 10.9–15.7 s into the notebook, and it is the only warning in each log.
A local run with only numpyro changed reproduces it. On 0.21.0 all cells pass. On 0.22.0, bayes_nonconj.md:338 (mcmc_ln = run_nuts(...)) fails with ValueError: BinomialProbs distribution got invalid probs parameter. The CI logs show only CellExecutionError, so the CI traceback itself is inferred. The reports artifacts that hold it expire after 7 days, and the first expires about 2026-09-25.
The timeout is a separate problem. 105510635506 was cancelled at exactly 120:00 even though bayes_nonconj passed in it. Two HTML builds of the same lecture sha, on full images rebuilt from the same sources, took 71.9 min (107515495294) and 116.5 min (107422724233). imp_sample (numba → JAX rewrite in caf3ddc, 2026-08-02) is 35–46% of the HTML time; phillips_drifts_volatilities and sargent_surico are next. Cancellations at 120 min have recurred on 08-03, 08-10, 08-17, 08-24, 08-31 and 09-07 (test-containers-lectures: lecture-python.myst doubled to the 120-minute ceiling #141), so the green 09-14 run was the exception.
The images are ruled out. They ship no jax, numpyro or arviz. The image from before 195b9f2 also passed bayes_nonconj on 09-18, before the upload, and 195b9f2 moved no Python package.
The lecture-python-intro lean failure on 09-18 (105510635540, observed_distributions) was a one-off. The same leg passed earlier that day and has been green since. The fetch that failed is unconfirmed; its err.log is artifact 10535844150, which expires about 2026-09-25 07:07Z.
Fixes
lecture-python.myst, the real fix: give the prior its true support. Tested on numpyro 0.21.0 and 0.22.0; all cells pass on both.
Pinning numpyro<0.22 in that cell is a stopgap only: it downgrades the environment for every later numpyro notebook in the build. init_strategy=init_to_median alone is not enough, because the later SVI cell fails the same way.
lecture-python.myst: make imp_sample fast on CPU again, either with its numba estimator or smaller sample sizes without a GPU.
QuantEcon/actions:
make timeout-minutes per repo in test-containers-lectures.yml (for example 180 for lecture-python.myst);
print reports/*.err.log in build-lectures' failure report, since myst-nb hides tracebacks and they otherwise live only in a short-lived artifact;
Fixing bayes_nonconj alone would still leave 2 of the 4 latest lecture-python.myst legs at the ceiling.
Release signal (#110 decision 4): QuantEcon/actions and its images did not cause this failure. Until both lecture-python.myst fixes land, a red lecture-python.myst leg says nothing about the images. The intro and advanced legs are still a valid signal.
lecture-python.myst · quantecon-build — failure after 108m
lecture-python.myst · quantecon — failure after 123m
Nobody was watching this run, so this issue is the alert. The run log shows what broke, and any job that uploads artifacts has attached its build output and failure reports to the run.
Close this issue once the workflow is green again — the next failure opens a fresh one.
lecture-python.myst · quantecon-build — failure after 94m
lecture-python.myst · quantecon — failure after 124m
Nobody was watching this run, so this issue is the alert. The run log shows what broke, and any job that uploads artifacts has attached its build output and failure reports to the run.
Close this issue once the workflow is green again — the next failure opens a fresh one.
Closing: the container test matrix is green again. Run 37256340227 on 2026-10-05 (4550f69) passed all eight legs. It is the first green run since 2026-09-14.
Both causes named in the 2026-09-24 triage are addressed:
#141 stays open. lecture-python.myst's build time is still the underlying problem, and its legs already use about three quarters of the new ceiling. A later failure opens a new alert.
Activity
github-actions commentedon Aug 24, 2026
🔴
Test Container Buildsfailedworkflow_runmainFailed jobs
lecture-python.myst · quantecon-build— cancelled after 120m (timed out, or the run was superseded)lecture-python.myst · quantecon— cancelled after 120m (timed out, or the run was superseded)Nobody was watching this run, so this issue is the alert. The run log shows what broke, and any job that uploads artifacts has attached its build output and failure reports to the run.
Close this issue once the workflow is green again — the next failure opens a fresh one.
github-actions commentedon Aug 31, 2026
🔴
Test Container Buildsfailedworkflow_runmainFailed jobs
lecture-python.myst · quantecon-build— cancelled after 120m (timed out, or the run was superseded)Nobody was watching this run, so this issue is the alert. The run log shows what broke, and any job that uploads artifacts has attached its build output and failure reports to the run.
Close this issue once the workflow is green again — the next failure opens a fresh one.
github-actions commentedon Sep 7, 2026
🔴
Test Container Buildsfailedworkflow_runmainFailed jobs
lecture-python.myst · quantecon-build— cancelled after 120m (timed out, or the run was superseded)Nobody was watching this run, so this issue is the alert. The run log shows what broke, and any job that uploads artifacts has attached its build output and failure reports to the run.
Close this issue once the workflow is green again — the next failure opens a fresh one.
github-actions commentedon Sep 18, 2026
🔴
Test Container Buildsfailedworkflow_runmainFailed jobs
lecture-python.myst · quantecon— cancelled after 107m (timed out, or the run was superseded)lecture-python.myst · quantecon-build— cancelled after 106m (timed out, or the run was superseded)Nobody was watching this run, so this issue is the alert. The run log shows what broke, and any job that uploads artifacts has attached its build output and failure reports to the run.
Close this issue once the workflow is green again — the next failure opens a fresh one.
github-actions commentedon Sep 18, 2026
🔴
Test Container Buildsfailedworkflow_runmainFailed jobs
lecture-python.myst · quantecon-build— cancelled after 120m (timed out, or the run was superseded)lecture-python-intro · quantecon-build— failure after 12mlecture-python.myst · quantecon— failure after 95mNobody was watching this run, so this issue is the alert. The run log shows what broke, and any job that uploads artifacts has attached its build output and failure reports to the run.
Close this issue once the workflow is green again — the next failure opens a fresh one.
github-actions commentedon Sep 21, 2026
🔴
Test Container Buildsfailedworkflow_runmainFailed jobs
lecture-python.myst · quantecon-build— cancelled after 120m (timed out, or the run was superseded)lecture-python.myst · quantecon— failure after 77mNobody was watching this run, so this issue is the alert. The run log shows what broke, and any job that uploads artifacts has attached its build output and failure reports to the run.
Close this issue once the workflow is green again — the next failure opens a fresh one.
github-actions commentedon Sep 23, 2026
🔴
Test Container Buildsfailedworkflow_runmainFailed jobs
lecture-python-intro · quantecon— failure after 23mlecture-python-advanced.myst · quantecon-build— cancelled after 25m (timed out, or the run was superseded)lecture-python.myst · quantecon— cancelled after 25m (timed out, or the run was superseded)lecture-python-advanced.myst · quantecon— cancelled after 25m (timed out, or the run was superseded)lecture-python-intro · quantecon-build— cancelled after 2m (timed out, or the run was superseded)lecture-python.myst · quantecon-build— cancelled after 25m (timed out, or the run was superseded)Nobody was watching this run, so this issue is the alert. The run log shows what broke, and any job that uploads artifacts has attached its build output and failure reports to the run.
Close this issue once the workflow is green again — the next failure opens a fresh one.
github-actions commentedon Sep 23, 2026
🔴
Test Container Buildsfailedworkflow_runmainFailed jobs
lecture-python-intro · quantecon-build— cancelled after 7m (timed out, or the run was superseded)lecture-python.myst · quantecon-build— cancelled after 7m (timed out, or the run was superseded)lecture-python-advanced.myst · quantecon— cancelled after 7m (timed out, or the run was superseded)lecture-python-advanced.myst · quantecon-build— cancelled after 7m (timed out, or the run was superseded)lecture-python.myst · quantecon— cancelled after 7m (timed out, or the run was superseded)lecture-python-intro · quantecon— cancelled after 7m (timed out, or the run was superseded)Nobody was watching this run, so this issue is the alert. The run log shows what broke, and any job that uploads artifacts has attached its build output and failure reports to the run.
Close this issue once the workflow is green again — the next failure opens a fresh one.
github-actions commentedon Sep 23, 2026
🔴
Test Container Buildsfailedworkflow_runmainFailed jobs
lecture-python.myst · quantecon— cancelled after 29m (timed out, or the run was superseded)lecture-python-advanced.myst · quantecon-build— cancelled after 29m (timed out, or the run was superseded)lecture-python-advanced.myst · quantecon— cancelled after 28m (timed out, or the run was superseded)lecture-python.myst · quantecon-build— cancelled after 28m (timed out, or the run was superseded)lecture-python-intro · quantecon-build— cancelled after 14m (timed out, or the run was superseded)Nobody was watching this run, so this issue is the alert. The run log shows what broke, and any job that uploads artifacts has attached its build output and failure reports to the run.
Close this issue once the workflow is green again — the next failure opens a fresh one.
github-actions commentedon Sep 24, 2026
🔴
Test Container Buildsfailedworkflow_runmainFailed jobs
lecture-python.myst · quantecon— failure after 118mlecture-python.myst · quantecon-build— failure after 95mNobody was watching this run, so this issue is the alert. The run log shows what broke, and any job that uploads artifacts has attached its build output and failure reports to the run.
Close this issue once the workflow is green again — the next failure opens a fresh one.
github-actions commentedon Sep 24, 2026
🔴
Test Container Buildsfailedworkflow_runmainFailed jobs
lecture-python.myst · quantecon— failure after 74mlecture-python.myst · quantecon-build— failure after 119mNobody was watching this run, so this issue is the alert. The run log shows what broke, and any job that uploads artifacts has attached its build output and failure reports to the run.
Close this issue once the workflow is green again — the next failure opens a fresh one.
quantecon-services commentedon Sep 24, 2026
Triage note, 2026-09-24. The latest run (35963034770, on
64aeb2f) is red for two separate reasons:lecture-python.mystlegs fail "Build HTML" with aCellExecutionErrorinlectures/bayes_nonconj.md. That is lecture content; no issue tracks it yet, and it belongs in QuantEcon/lecture-python.myst.quantecon-buildleg also used 116 of its 120 minutes on notebooks. That is test-containers-lectures: lecture-python.myst doubled to the 120-minute ceiling #141.imp_samplealone took 31.7 of 70 minutes onquanteconand 43.1 of 116 onquantecon-build.The work to make this matrix trustworthy is now tracked by the Project #188 (#102, #141, #142). This alert stays unparented and should close once a run is green.
Generated by Claude Code
quantecon-services commentedon Sep 24, 2026
Why this has been red since 2026-09-18. Two problems in lecture-python.myst cause it. Neither is in QuantEcon/actions or its images.
bayes_nonconjfails since numpyro 0.22.0 (PyPI, 2026-09-18 08:51Z), which the lecture installs unpinned (!pip install numpyro jax arviz, bayes_nonconj.md:24). 0.22.0 validates distribution arguments by default. The truncated log-normal prior (truncated_lognormal(), bayes_nonconj.md:333-336) is anExpTransformof aTruncatedNormal(high=0). Its declared support is Positive rather than (0, 1], so NUTS initialisation can propose θ > 1, anddist.Binomialnow raises.timeout-minutes, so whether a leg passes depends on the runner it lands on.Tested repos, each on
quanteconandquantecon-build: lecture-python-intro, lecture-python.myst, lecture-python-advanced.myst. lecture-jax is commented out.Evidence
bayes_nonconjpassed at 07:05Z, before the upload (105510635506). It failed at 09:02Z, after it (105510635773). The lecture file has not changed since June. Every run since has failed it, on both images, 10.9–15.7 s into the notebook, and it is the only warning in each log.mcmc_ln = run_nuts(...)) fails withValueError: BinomialProbs distribution got invalid probs parameter.The CI logs show onlyCellExecutionError, so the CI traceback itself is inferred. The reports artifacts that hold it expire after 7 days, and the first expires about 2026-09-25.bayes_nonconjpassed in it. Two HTML builds of the same lecture sha, on full images rebuilt from the same sources, took 71.9 min (107515495294) and 116.5 min (107422724233).imp_sample(numba → JAX rewrite in caf3ddc, 2026-08-02) is 35–46% of the HTML time;phillips_drifts_volatilitiesandsargent_suricoare next. Cancellations at 120 min have recurred on 08-03, 08-10, 08-17, 08-24, 08-31 and 09-07 (test-containers-lectures: lecture-python.myst doubled to the 120-minute ceiling #141), so the green 09-14 run was the exception.bayes_nonconjon 09-18, before the upload, and 195b9f2 moved no Python package.observed_distributions) was a one-off. The same leg passed earlier that day and has been green since. The fetch that failed is unconfirmed; its err.log is artifact 10535844150, which expires about 2026-09-25 07:07Z.Fixes
numpyro<0.22in that cell is a stopgap only: it downgrades the environment for every later numpyro notebook in the build.init_strategy=init_to_medianalone is not enough, because the later SVI cell fails the same way.imp_samplefast on CPU again, either with its numba estimator or smaller sample sizes without a GPU.timeout-minutesper repo intest-containers-lectures.yml(for example 180 for lecture-python.myst);reports/*.err.loginbuild-lectures' failure report, since myst-nb hides tracebacks and they otherwise live only in a short-lived artifact;Fixing
bayes_nonconjalone would still leave 2 of the 4 latest lecture-python.myst legs at the ceiling.Release signal (#110 decision 4): QuantEcon/actions and its images did not cause this failure. Until both lecture-python.myst fixes land, a red lecture-python.myst leg says nothing about the images. The intro and advanced legs are still a valid signal.
Generated by Claude Code
feat(build-lectures): print failed notebooks' tracebacks in the failu…
ci(lecture-validation): a per-repo timeout, 180 min for lecture-pytho…
github-actions commentedon Sep 25, 2026
🔴
Test Container Buildsfailedworkflow_runmainFailed jobs
lecture-python.myst · quantecon-build— failure after 108mlecture-python.myst · quantecon— failure after 123mNobody was watching this run, so this issue is the alert. The run log shows what broke, and any job that uploads artifacts has attached its build output and failure reports to the run.
Close this issue once the workflow is green again — the next failure opens a fresh one.
github-actions commentedon Sep 28, 2026
🔴
Test Container Buildsfailedworkflow_runmainFailed jobs
lecture-python.myst · quantecon-build— failure after 94mlecture-python.myst · quantecon— failure after 124mNobody was watching this run, so this issue is the alert. The run log shows what broke, and any job that uploads artifacts has attached its build output and failure reports to the run.
Close this issue once the workflow is green again — the next failure opens a fresh one.
docs(plan): cite the lecture-side fix, not the CI alert, in the #102 row
docs(plan): record #102 as closed by #203, and the run that exercised…
mmcky commentedon Oct 5, 2026
Closing: the container test matrix is green again. Run 37256340227 on 2026-10-05 (
4550f69) passed all eight legs. It is the first green run since 2026-09-14.Both causes named in the 2026-09-24 triage are addressed:
bayes_nonconjunder numpyro 0.22. The truncated log-normal prior now declares its (0, 1] support (bayes_nonconj: declare the truncated log-normal prior's (0, 1] support (numpyro 0.22)Â lecture-python.myst#1065, merged 2026-10-05 01:55Z, before this run).#141 stays open. lecture-python.myst's build time is still the underlying problem, and its legs already use about three quarters of the new ceiling. A later failure opens a new alert.
qe: correct the review record after an independent compliance check
docs(plan): catch up with the v0.12.0 follow-ups and the 2026-11-04 d…