Skip to content

Fix multi-channel compositing and add per-channel norm support #1266

Fix multi-channel compositing and add per-channel norm support

Fix multi-channel compositing and add per-channel norm support #1266

Triggered via pull request March 19, 2026 18:46
Status Cancelled
Total duration 4m 16s
Artifacts 3

test.yaml

on: pull_request
get-environments
8s
get-environments
Matrix: test
Tests pass in all hatch environments
5s
Tests pass in all hatch environments
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 3 warnings
hatch-test.py3.14-pre (PRE-RELEASE DEPENDENCIES)
Process completed with exit code 1.
hatch-test.py3.11-stable
Canceling since a higher priority waiting request for Test-refs/pull/451/merge exists
hatch-test.py3.11-stable
Process completed with exit code 1.
hatch-test.py3.14-stable
Canceling since a higher priority waiting request for Test-refs/pull/451/merge exists
hatch-test.py3.14-stable
The operation was canceled.
Tests pass in all hatch environments
Process completed with exit code 1.
Test
Canceling since a higher priority waiting request for Test-refs/pull/451/merge exists
hatch-test.py3.14-pre (PRE-RELEASE DEPENDENCIES)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
hatch-test.py3.11-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
hatch-test.py3.14-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

Artifacts

Produced during runtime
Name Size Digest
visual_test_results_hatch-test.py3.11-stable
12.3 MB
sha256:6a576ff4523ca6d640fe9108fc7d65e640ed6b8655a8496e4bdf9071ea4b0792
visual_test_results_hatch-test.py3.14-pre
12.3 MB
sha256:ed1056745751aaff21dfd3a1f3af204a5f59cb940ab4b7b018256f1e5663e45b
visual_test_results_hatch-test.py3.14-stable
9.86 MB
sha256:1b808cb8712f3e48e3bc940ee728b0b38c688c5d945ca28d54ac5ff2602fece8