Skip to content
Test

Fix render_points crash when coloring by spatial coord (x/y) #1611

Sign in to view logs

Fix render_points crash when coloring by spatial coord (x/y)

Fix render_points crash when coloring by spatial coord (x/y) #1611

Triggered via pull request May 19, 2026 23:38
@timtreistimtreis
opened #671
fix/issue-613-render-points-color-coord
Status Success
Total duration 6m 33s
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

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.8 MB
sha256:53584333c81188a9d8b433c1f0985f6b35bf700c464880e9485d4f8163eeaef2
visual_test_results_hatch-test.py3.14-pre
25.3 MB
sha256:b06bd263d743d0e9fe46ec018ba77fed3be385f4ba57bce252af1563ebbeb803
visual_test_results_hatch-test.py3.14-stable
14.8 MB
sha256:e4db7fff1c45947b76bba6732b5e8d2021941b03da7db828e8028ffe4a8fd3d1