Skip to content

Support channels_as_legend for single-channel and sequential renders #1486

Support channels_as_legend for single-channel and sequential renders

Support channels_as_legend for single-channel and sequential renders #1486

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

test.yaml

on: pull_request
get-environments
7s
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

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.1 MB
sha256:bdf12975711bd157d26ea615b92c725150aa8511d1390820e144d64dc77b4f45
visual_test_results_hatch-test.py3.14-pre
24.2 MB
sha256:dbbe1dfb0f9b514e24c4f946723a2ba972ed19651d3913b28c25192188b64e19
visual_test_results_hatch-test.py3.14-stable
14.1 MB
sha256:3e27cf78617cf20cd6441483e0011dfbd6c80cd7fdcb27ce93cba5564a422394