From 119b0d7a150eae28df0f51996d3f69e498c77d4b Mon Sep 17 00:00:00 2001 From: Matt McKay Date: Wed, 11 Nov 2026 12:18:32 +1100 Subject: [PATCH] CI: upload execution reports from the build that executes notebooks The "Upload Execution Reports" step only looked in _build/html/reports. Since #588 made the tojupyter build the gating step, a CellExecutionError stops the job in that build, which writes its reports to _build/jupyter/reports, so the execution-reports artifact came up empty. Upload the reports directories of all three builds. Mirrors QuantEcon/lecture-python-advanced.myst#410. Co-Authored-By: Claude Opus 5.5 --- .github/workflows/ci.yml | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 4b1dcda3..feadbe2a 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -100,12 +100,19 @@ jobs: shell: bash -l {0} run: | jb build lectures --path-output ./ -n -W --keep-going + # Notebooks execute in whichever `jb build` runs them first, and each build + # writes its execution reports under its own output directory. Since the + # tojupyter build gates (see above), a CellExecutionError stops the job there + # and its traceback is only in _build/jupyter/reports, so upload all three. - name: Upload Execution Reports uses: actions/upload-artifact@v7 if: failure() with: name: execution-reports - path: _build/html/reports + path: | + _build/jupyter/reports + _build/latex/reports + _build/html/reports - name: Preview Deploy to Netlify uses: nwtgck/actions-netlify@v4 with: