Skip to content

Add tiling QC metric for tile-boundary segmentation artifacts #630

Add tiling QC metric for tile-boundary segmentation artifacts

Add tiling QC metric for tile-boundary segmentation artifacts #630

Triggered via pull request April 11, 2026 12:40
Status Cancelled
Total duration 1m 17s
Artifacts

test.yaml

on: pull_request
get-environments
8s
get-environments
ensure-data-is-cached
1m 5s
ensure-data-is-cached
Matrix: test
Coverage (ubuntu-latest, hatch-test.py3.13-stable)
0s
Coverage (ubuntu-latest, hatch-test.py3.13-stable)
Tests pass in all hatch environments
4s
Tests pass in all hatch environments
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 1 warning
ensure-data-is-cached
Canceling since a higher priority waiting request for Test-refs/pull/1157/merge exists
ensure-data-is-cached
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/1157/merge exists
ensure-data-is-cached
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/