docs(mkdocs-deploy): add a notebooks-continue-on-error usage example #173
MAfarragtest-mkdocs-deploy.yml
on: push
Test Main Branch Trigger
13s
Test Error Scenarios
14s
Test Git Configuration
17s
Test Package Manager Command Execution
25s
Test Release Tag Resolution
15s
Test Notebooks Skipped When notebooks-path Empty
18s
Test Notebook Exclude Globs
42s
Test Notebook Continue-On-Error
54s
Matrix: Test Custom Configuration
Matrix: Test Default install-groups Value
Matrix: Test install-groups Format Variations
Matrix: Test Pixi Environment Names
Matrix: Test Pull Request Trigger
Matrix: Test Python Version Compatibility
Matrix: Test Release Trigger
Matrix: Test Notebook Execution
Annotations
4 errors and 11 warnings
|
Test Error Scenarios
Process completed with exit code 2.
|
|
Test Error Scenarios
Process completed with exit code 2.
|
|
Test Error Scenarios
Process completed with exit code 2.
|
|
Test Notebook Continue-On-Error
Process completed with exit code 1.
|
|
Test Error Scenarios
No file matched to [/home/runner/work/github-actions/github-actions/uv.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
|
Test Error Scenarios
No 'groups:' or 'extras:' sections found. Please use format: 'groups: name1 name2, extras: extra1 extra2'
|
|
Test Error Scenarios
No file matched to [/home/runner/work/github-actions/github-actions/uv.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
|
Test Error Scenarios
No file matched to [/home/runner/work/github-actions/github-actions/uv.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
|
|
Test Notebook Execution (pip)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test Notebook Continue-On-Error
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test Notebook Continue-On-Error
1 notebook(s) failed to execute but were tolerated (notebooks-continue-on-error=true); their docs will show stale or missing outputs.
|
|
Test Notebook Continue-On-Error
Notebook execution failed, continuing: docs/notebook/flaky.ipynb (Command '['/home/runner/work/github-actions/github-actions/.venv/bin/python3', '-m', 'jupyter', 'nbconvert', '--to', 'notebook', '--execute', '--inplace', '--ExecutePreprocessor.timeout=600', 'docs/notebook/flaky.ipynb']' returned non-zero exit status 1.)
|
|
Test Notebook Exclude Globs
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test Notebook Execution (uv)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test Notebook Execution (pixi)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|