Skip to content
unittest

fix(gapic-generator): [Approach 1] thread default_host to OTel helpers instead of mutating client_options #22680

Sign in to view logs

fix(gapic-generator): [Approach 1] thread default_host to OTel helpers instead of mutating client_options

fix(gapic-generator): [Approach 1] thread default_host to OTel helpers instead of mutating client_options #22680

Triggered via pull request October 30, 2026 21:55
@chalmerlowechalmerlowe
opened #18933
fix/otel-default-host-param
Status Failure
Total duration 6m 8s
Artifacts 18

unittest.yml

on: pull_request
initialize
42s
initialize
Matrix: core-deps
Matrix: unit
all-tests
3s
all-tests
cover
0s
cover
Fit to window
Zoom out
Zoom in

Annotations

101 errors, 66 warnings, and 2 notices
unit (3.11, Shard 1)
Process completed with exit code 124.
unit (3.14, Shard 9)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.15, Shard 9)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.10, Shard 9)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.14, Shard 3)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.10, Shard 1)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.10, Shard 1)
Process completed with exit code 124.
unit (3.14, Shard 8)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.11, Shard 9)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.13, Shard 3)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.12, Shard 9)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.13, Shard 9)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.11, Shard 3)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.12, Shard 1)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.12, Shard 1)
Process completed with exit code 124.
unit (3.13, Shard 1)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.13, Shard 1)
Process completed with exit code 124.
unit (3.15, Shard 1)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.15, Shard 1)
Process completed with exit code 124.
unit (3.15, Shard 8)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.10, Shard 8)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.12, Shard 8)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.15, Shard 6)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.15, Shard 3)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.10, Shard 6)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.11, Shard 6)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.14, Shard 6)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.12, Shard 3)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.12, Shard 3)
The operation was canceled.
unit (3.14, Shard 1)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.14, Shard 1)
The operation was canceled.
unit (3.15, Shard 2)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.15, Shard 2)
The operation was canceled.
unit (3.11, Shard 8)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.11, Shard 8)
The operation was canceled.
unit (3.12, Shard 2)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.12, Shard 2)
The operation was canceled.
unit (3.13, Shard 8)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.13, Shard 8)
The operation was canceled.
unit (3.13, Shard 6)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.13, Shard 6)
The operation was canceled.
unit (3.14, Shard 5)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.14, Shard 5)
The operation was canceled.
unit (3.15, Shard 4)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.15, Shard 4)
The operation was canceled.
unit (3.12, Shard 4)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.12, Shard 4)
The operation was canceled.
unit (3.13, Shard 7)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.13, Shard 7)
The operation was canceled.
unit (3.15, Shard 7)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.15, Shard 7)
The operation was canceled.
unit (3.14, Shard 4)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.14, Shard 4)
The operation was canceled.
unit (3.15, Shard 5)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.15, Shard 5)
The operation was canceled.
unit (3.10, Shard 7)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.10, Shard 7)
The operation was canceled.
unit (3.10, Shard 3)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.10, Shard 3)
The operation was canceled.
unit (3.11, Shard 5)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.11, Shard 5)
The operation was canceled.
unit (3.10, Shard 5)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.10, Shard 5)
The operation was canceled.
unit (3.14, Shard 2)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.14, Shard 2)
The operation was canceled.
unit (3.11, Shard 2)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.11, Shard 2)
The operation was canceled.
unit (3.11, Shard 4)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.11, Shard 4)
The operation was canceled.
unit (3.12, Shard 7)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.10, Shard 2)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.12, Shard 7)
The operation was canceled.
unit (3.10, Shard 2)
The operation was canceled.
unit (3.12, Shard 6)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.12, Shard 6)
The operation was canceled.
unit (3.13, Shard 4)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.13, Shard 4)
The operation was canceled.
unit (3.10, Shard 4)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.10, Shard 4)
The operation was canceled.
unit (3.12, Shard 5)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.12, Shard 5)
The operation was canceled.
unit (3.14, Shard 7)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.14, Shard 7)
The operation was canceled.
unit (3.11, Shard 7)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.11, Shard 7)
The operation was canceled.
unit (3.13, Shard 2)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.13, Shard 2)
The operation was canceled.
unit (3.13, Shard 5)
The strategy configuration was canceled because "unit._3_11_Shard_1_1_bigquery-" failed
unit (3.13, Shard 5)
The operation was canceled.
core-deps handwritten (3.14, Shard 1)
Process completed with exit code 124.
core-deps handwritten (3.14, Shard 7)
The strategy configuration was canceled because "core-deps._3_14_Shard_1_1_bigquery-" failed
core-deps handwritten (3.14, Shard 6)
The strategy configuration was canceled because "core-deps._3_14_Shard_1_1_bigquery-" failed
core-deps handwritten (3.14, Shard 2)
The strategy configuration was canceled because "core-deps._3_14_Shard_1_1_bigquery-" failed
core-deps handwritten (3.14, Shard 2)
The operation was canceled.
core-deps handwritten (3.14, Shard 5)
The strategy configuration was canceled because "core-deps._3_14_Shard_1_1_bigquery-" failed
core-deps handwritten (3.14, Shard 5)
The operation was canceled.
core-deps handwritten (3.14, Shard 4)
The strategy configuration was canceled because "core-deps._3_14_Shard_1_1_bigquery-" failed
core-deps handwritten (3.14, Shard 4)
The operation was canceled.
core-deps handwritten (3.14, Shard 8)
The strategy configuration was canceled because "core-deps._3_14_Shard_1_1_bigquery-" failed
core-deps handwritten (3.14, Shard 8)
The operation was canceled.
all-tests
Process completed with exit code 1.
initialize
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@11d5960a326750d5838078e36cf38b85af677262, actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.11, Shard 1)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.14, Shard 9)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.15, Shard 9)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.15, Shard 9)
Cache folder path is retrieved for pip but doesn't exist on disk: /home/runner/.cache/pip. This likely indicates that there are no dependencies to cache. Consider removing the cache step if it is not needed.
unit (3.10, Shard 9)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.14, Shard 3)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.14, Shard 3)
Cache folder path is retrieved for pip but doesn't exist on disk: /home/runner/.cache/pip. This likely indicates that there are no dependencies to cache. Consider removing the cache step if it is not needed.
unit (3.10, Shard 1)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.14, Shard 8)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.14, Shard 8)
Cache folder path is retrieved for pip but doesn't exist on disk: /home/runner/.cache/pip. This likely indicates that there are no dependencies to cache. Consider removing the cache step if it is not needed.
unit (3.11, Shard 9)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.13, Shard 3)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.13, Shard 3)
Cache folder path is retrieved for pip but doesn't exist on disk: /home/runner/.cache/pip. This likely indicates that there are no dependencies to cache. Consider removing the cache step if it is not needed.
unit (3.12, Shard 9)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.13, Shard 9)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.11, Shard 3)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.11, Shard 3)
Cache folder path is retrieved for pip but doesn't exist on disk: /home/runner/.cache/pip. This likely indicates that there are no dependencies to cache. Consider removing the cache step if it is not needed.
unit (3.12, Shard 1)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.13, Shard 1)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.15, Shard 1)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.15, Shard 8)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.15, Shard 8)
Cache folder path is retrieved for pip but doesn't exist on disk: /home/runner/.cache/pip. This likely indicates that there are no dependencies to cache. Consider removing the cache step if it is not needed.
unit (3.10, Shard 8)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.12, Shard 8)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.12, Shard 8)
Cache folder path is retrieved for pip but doesn't exist on disk: /home/runner/.cache/pip. This likely indicates that there are no dependencies to cache. Consider removing the cache step if it is not needed.
unit (3.15, Shard 6)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.15, Shard 6)
Cache folder path is retrieved for pip but doesn't exist on disk: /home/runner/.cache/pip. This likely indicates that there are no dependencies to cache. Consider removing the cache step if it is not needed.
unit (3.15, Shard 3)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.15, Shard 3)
Cache folder path is retrieved for pip but doesn't exist on disk: /home/runner/.cache/pip. This likely indicates that there are no dependencies to cache. Consider removing the cache step if it is not needed.
unit (3.10, Shard 6)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.11, Shard 6)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.11, Shard 6)
Cache folder path is retrieved for pip but doesn't exist on disk: /home/runner/.cache/pip. This likely indicates that there are no dependencies to cache. Consider removing the cache step if it is not needed.
unit (3.14, Shard 6)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.14, Shard 6)
Cache folder path is retrieved for pip but doesn't exist on disk: /home/runner/.cache/pip. This likely indicates that there are no dependencies to cache. Consider removing the cache step if it is not needed.
unit (3.12, Shard 3)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.14, Shard 1)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.15, Shard 2)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.11, Shard 8)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.12, Shard 2)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.13, Shard 8)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.13, Shard 6)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.14, Shard 5)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.15, Shard 4)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.12, Shard 4)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.13, Shard 7)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.15, Shard 7)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.14, Shard 4)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.15, Shard 5)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.10, Shard 7)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.10, Shard 3)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.11, Shard 5)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.10, Shard 5)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.14, Shard 2)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.11, Shard 2)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.11, Shard 4)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.12, Shard 7)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.10, Shard 2)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.12, Shard 6)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.13, Shard 4)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.10, Shard 4)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.12, Shard 5)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.14, Shard 7)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.11, Shard 7)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.13, Shard 2)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.13, Shard 5)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
initialize
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
all-tests
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"

Artifacts

Produced during runtime
Name Size Digest
coverage-artifact-3.10-6
1.67 MB
sha256:9eb69e754228a60f9afa1f0b4f6d023fda967180b09a9399cb813136c4b796cd
coverage-artifact-3.10-8
2.56 MB
sha256:35e13345fc6c76ef9a0e7752d4bf30412ce416a80c9ff3410aaa721a529c9d4f
coverage-artifact-3.10-9
124 KB
sha256:52e139bc14ddafa065dcad7c7150b06bdd62162e1a320f6af2874cc93ceb1fe2
coverage-artifact-3.11-3
1.47 MB
sha256:946984363cb660211090314be1e929c85e358e95cfa2d4148af9c735b903c809
coverage-artifact-3.11-6
1.73 MB
sha256:2aed33c6e30265dad229862c8add07c193a29358bf049092f76fa68d3d46d7f4
coverage-artifact-3.11-9
126 KB
sha256:8bc829e17c7d9a099add90fd52d540bf3e9bdd0a2c2b0a55498f9d956364925a
coverage-artifact-3.12-8
2.56 MB
sha256:e524ffffce68416ee154ccd62f7ce283209eb57b7cea78c58b66a9afc760a76c
coverage-artifact-3.12-9
124 KB
sha256:bdf95a801036286952a99d234c2ad320bc4106476411deb79fde8bfa868617de
coverage-artifact-3.13-3
1.46 MB
sha256:84cd00cd9e525ebe232a2fee7c4f1f0dc41e52fcefcd5d669e98a5f0c9d362df
coverage-artifact-3.13-9
124 KB
sha256:01a9ff311cb8f523b0193f18b44a4172f3d4439b3f44a4f3ff89bed7e6e67cbf
coverage-artifact-3.14-3
1.3 MB
sha256:d35b9fb55aaab5c3dae4d7ed59592d476a2aeea8aeb4fca4e7949844047181b1
coverage-artifact-3.14-6
1.49 MB
sha256:108643dffd92dd79a4550715ec362edc28dde693adfcda94121362b9b2ba4464
coverage-artifact-3.14-8
2.15 MB
sha256:8c9d8cb5b76dfc417007e2cae20e9a3020e78c0ccd1ab238f33a8640b212f2d8
coverage-artifact-3.14-9
115 KB
sha256:0dc5cf43e92d07517953a5124c33d4fa46fb8197e301b382d6be02818d1f6a63
coverage-artifact-3.15-3
1.3 MB
sha256:7505c8590bfeb5d50f88dc223a1e765c928e92c5986dff639fccde4e0d41ba89
coverage-artifact-3.15-6
1.49 MB
sha256:2e27599af9831ee5a05eb338810018d30693dc84659fb9de7469eb4b5b97663b
coverage-artifact-3.15-8
2.14 MB
sha256:2f3edac454b811934817489ca018a0f4a998e5b1a7fe8c723951f41499438cf9
coverage-artifact-3.15-9
115 KB
sha256:c90d1b5ecc334d3487393c67b4156a9db3708df3bdd32479018e34b2c3b413d5