Skip to content

MAINT: Fix notation on python_min (#2545) #2380

MAINT: Fix notation on python_min (#2545)

MAINT: Fix notation on python_min (#2545) #2380

Triggered via push March 16, 2026 14:49
Status Failure
Total duration 9m 19s
Artifacts 6

ci.yml

on: push
should run ci
8s
should run ci
cache-pixi-lock
9s
cache-pixi-lock
Matrix: integration-test
Matrix: unit-test
TypeChecking: pixi run typing
29s
TypeChecking: pixi run typing
build-and-upload-nightly-parcels
1m 27s
build-and-upload-nightly-parcels
merge-test-artifacts
0s
merge-test-artifacts
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 10 warnings
ty (invalid-return-type): src/parcels/_core/index_search.py#L47
src/parcels/_core/index_search.py:47:16: invalid-return-type: Return type does not match returned value: expected `tuple[int, int]`, found `tuple[Unknown, ndarray[tuple[Any, ...], dtype[Any]]]` src/parcels/_core/index_search.py:24:6: Expected `tuple[int, int]` because of return type info: rule `invalid-return-type` is enabled by default
ty (not-iterable): src/parcels/_core/fieldset.py#L484
src/parcels/_core/fieldset.py:484:26: not-iterable: Object of type `None` is not iterable info: It doesn't have an `__iter__` method or a `__getitem__` method info: rule `not-iterable` is enabled by default
ty (invalid-assignment): src/parcels/_core/fieldset.py#L484
src/parcels/_core/fieldset.py:484:5: invalid-assignment: Too many values to unpack: Expected 2 src/parcels/_core/fieldset.py:484:26: Got 3 info: rule `invalid-assignment` is enabled by default
ty (invalid-assignment): src/parcels/_core/fieldset.py#L423
src/parcels/_core/fieldset.py:423:22: invalid-assignment: Object of type `Dataset` is not assignable to `UxDataset` src/parcels/_core/fieldset.py:423:17: Declared type `UxDataset` info: rule `invalid-assignment` is enabled by default
ty (invalid-assignment): src/parcels/_core/fieldset.py#L404
src/parcels/_core/fieldset.py:404:22: invalid-assignment: Object of type `Dataset` is not assignable to `UxDataset` src/parcels/_core/fieldset.py:404:17: Declared type `UxDataset` info: rule `invalid-assignment` is enabled by default
ty (unresolved-attribute): src/parcels/_core/fieldset.py#L357
src/parcels/_core/fieldset.py:357:175: unresolved-attribute: Attribute `left` is not defined on `None` in union `Unknown | TimeInterval | None` info: rule `unresolved-attribute` is enabled by default
ty (invalid-argument-type): src/parcels/_core/fieldset.py#L210
src/parcels/_core/fieldset.py:210:34: invalid-argument-type: Argument to bound method `__init__` is incorrect: Expected `UxDataArray`, found `DataArray` src/parcels/_core/uxgrid.py:21:9: info: Method defined here src/parcels/_core/uxgrid.py:21:44: Parameter declared here info: rule `invalid-argument-type` is enabled by default
ty (unresolved-attribute): src/parcels/_core/field.py#L161
src/parcels/_core/field.py:161:20: unresolved-attribute: Attribute `zdim` is not defined on `UxGrid` in union `Unknown | UxGrid | XGrid` info: rule `unresolved-attribute` is enabled by default
ty (unresolved-attribute): src/parcels/_core/field.py#L154
src/parcels/_core/field.py:154:20: unresolved-attribute: Attribute `ydim` is not defined on `UxGrid` in union `Unknown | UxGrid | XGrid` info: rule `unresolved-attribute` is enabled by default
ty (unresolved-attribute): src/parcels/_core/field.py#L147
src/parcels/_core/field.py:147:20: unresolved-attribute: Attribute `xdim` is not defined on `UxGrid` in union `Unknown | UxGrid | XGrid` info: rule `unresolved-attribute` is enabled by default
build-and-upload-nightly-parcels
Process completed with exit code 1.
cache-pixi-lock
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
ty (redundant-cast): src/parcels/_core/xgrid.py#L379
src/parcels/_core/xgrid.py:379:24: redundant-cast: Value is already of type `Literal["X", "Y", "Z"]` info: rule `redundant-cast` is enabled by default
Unit tests: ubuntu | pixi run -e test tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Unit tests: ubuntu | pixi run -e test-minimum tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Unit tests: ubuntu | pixi run -e test-minimum tests
Cache save failed.
Unit tests: ubuntu | pixi run -e test-py311 tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Unit tests: ubuntu | pixi run -e test-py311 tests
Cache save failed.
Unit tests: ubuntu | pixi run -e test-py313 tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Unit tests: ubuntu | pixi run -e test-py313 tests
Cache save failed.
Unit tests: windows | pixi run -e test tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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
Unittest report ubuntu-test
25.1 KB
sha256:17d3c65041bb32cfaa46635b0c25db26a4b90fe6d5f967fe1fb77653e7a9b9ed
Unittest report ubuntu-test-minimum
25.2 KB
sha256:0fc78fc34f50275b3d7e3bc53ec674195be9827b627c4d4ab9659717632c8997
Unittest report ubuntu-test-py311
25.4 KB
sha256:c1430d3a8d336b2ddd849fe4887ae3d5506aab105d20e724d3dc2d15d3513498
Unittest report ubuntu-test-py313
25.4 KB
sha256:c2f835eaae9b95111c9a2eb5c7f6d050d4f96f32a5749e02fbc531e803c5fb38
Unittest report windows-test
25.6 KB
sha256:4054f40c385b638c26a6b0466fe23fd286a2204f48bcce42ce71d9703c96f7cf
pixi-lock
243 KB
sha256:6b2d87171c13a4673708225b70ff6531e3b6efc2836485a1ad6032d33df6f8da