Skip to content

Support channels_as_legend for single-channel and sequential renders #1488

Support channels_as_legend for single-channel and sequential renders

Support channels_as_legend for single-channel and sequential renders #1488

Triggered via pull request May 7, 2026 19:16
Status Failure
Total duration 6m 11s
Artifacts 3

test.yaml

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

Annotations

4 errors and 3 warnings
hatch-test.py3.14-pre (PRE-RELEASE DEPENDENCIES)
Process completed with exit code 1.
hatch-test.py3.11-stable
Process completed with exit code 1.
hatch-test.py3.14-stable
Process completed with exit code 1.
Tests pass in all hatch environments
Process completed with exit code 1.
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. 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/
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. 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/
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. 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/

Artifacts

Produced during runtime
Name Size Digest
visual_test_results_hatch-test.py3.11-stable
14.2 MB
sha256:6f69756aea61cc339fb9670bd86a7c632222c827b8daf37281e9f51554490cfe
visual_test_results_hatch-test.py3.14-pre
24.2 MB
sha256:85a98d3cfdd11b41efcdc2117767827a8d18e4689a1acb4980081789e440a61b
visual_test_results_hatch-test.py3.14-stable
14.2 MB
sha256:94a2a63de947b197467467c4b17bab1670fba8e9a926ac2cb072df83c3b46536