Skip to content

geotiff: reject band=True/False on all read paths (#1786) (#1791) #1708

geotiff: reject band=True/False on all read paths (#1786) (#1791)

geotiff: reject band=True/False on all read paths (#1786) (#1791) #1708

Triggered via push May 13, 2026 14:58
Status Failure
Total duration 6m 16s
Artifacts

test.yml

on: push
Matrix: run
Fit to window
Zoom out
Zoom in

Annotations

14 errors, 6 warnings, and 3 notices
run (macos-latest, 3.14)
The strategy configuration was canceled because "run.ubuntu-latest_3_13" failed
run (ubuntu-latest, 3.13)
The operation was canceled.
run (macos-latest, 3.13)
The strategy configuration was canceled because "run.ubuntu-latest_3_13" failed
run (macos-latest, 3.12)
The strategy configuration was canceled because "run.ubuntu-latest_3_13" failed
run (ubuntu-latest, 3.14)
The strategy configuration was canceled because "run.ubuntu-latest_3_13" failed
run (ubuntu-latest, 3.14)
The operation was canceled.
run (ubuntu-latest, 3.12)
The strategy configuration was canceled because "run.ubuntu-latest_3_13" failed
run (ubuntu-latest, 3.12)
The operation was canceled.
run (windows-latest, 3.12)
The strategy configuration was canceled because "run.ubuntu-latest_3_13" failed
run (windows-latest, 3.12)
The operation was canceled.
run (windows-latest, 3.14)
The strategy configuration was canceled because "run.ubuntu-latest_3_13" failed
run (windows-latest, 3.14)
The operation was canceled.
run (windows-latest, 3.13)
The strategy configuration was canceled because "run.ubuntu-latest_3_13" failed
run (windows-latest, 3.13)
The operation was canceled.
run (ubuntu-latest, 3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
run (ubuntu-latest, 3.14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
run (ubuntu-latest, 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
run (windows-latest, 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
run (windows-latest, 3.14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
run (windows-latest, 3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
run (windows-latest, 3.12)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
run (windows-latest, 3.14)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
run (windows-latest, 3.13)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026