Skip to content
Test

Support channels_as_legend for single-channel and sequential renders #1490

Sign in to view logs

Support channels_as_legend for single-channel and sequential renders

Support channels_as_legend for single-channel and sequential renders #1490

Triggered via pull request May 7, 2026 19:40
@timtreistimtreis
synchronize #641
fix/issue-601-channels-as-legend-single-channel
Status Success
Total duration 6m 53s
Artifacts 3

test.yaml

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

Annotations

1 error and 3 warnings
hatch-test.py3.14-pre (PRE-RELEASE DEPENDENCIES)
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, 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:00221ac1b01cfdd574dd08c86344e8e2166dbfafae4df0d5950acf5f13e09acb
visual_test_results_hatch-test.py3.14-pre
24.3 MB
sha256:40c79ba4087af06d91590a92393926f3050997a6ebecc190349b947f0b565f80
visual_test_results_hatch-test.py3.14-stable
14.2 MB
sha256:c32fbbf00ebfdaf3389003bf3765583b7e7dd2089b15ea369ddd3e3d04182e6f