Skip to content

Fix issue where single object returns object itself #3102

Fix issue where single object returns object itself

Fix issue where single object returns object itself #3102

Triggered via pull request March 30, 2026 20:57
Status Failure
Total duration 11m 57s
Artifacts 3

main.yml

on: pull_request
run-if-changes
5s
run-if-changes
Matrix: build
build-success
3s
build-success
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 7 warnings
Coverage
Process completed with exit code 1.
build (3.12, 3.10) / Compare baseline Python 3.12 with MPL 3.10
Process completed with exit code 1.
build (3.10, 3.9) / Compare baseline Python 3.10 with MPL 3.9
Process completed with exit code 1.
build (3.14, 3.10) / Compare baseline Python 3.14 with MPL 3.10
Process completed with exit code 1.
build (3.12, 3.10) / Test Python 3.12 with MPL 3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: mamba-org/setup-micromamba@v2.0.7. 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/
build (3.10, 3.9) / Test Python 3.10 with MPL 3.9
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: mamba-org/setup-micromamba@v2.0.7. 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/
build (3.14, 3.10) / Test Python 3.14 with MPL 3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: mamba-org/setup-micromamba@v2.0.7. 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/
Coverage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: mamba-org/setup-micromamba@v2.0.7. 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/
build (3.12, 3.10) / Compare baseline Python 3.12 with MPL 3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: mamba-org/setup-micromamba@v2.0.7. 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/
build (3.10, 3.9) / Compare baseline Python 3.10 with MPL 3.9
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: mamba-org/setup-micromamba@v2.0.7. 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/
build (3.14, 3.10) / Compare baseline Python 3.14 with MPL 3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: mamba-org/setup-micromamba@v2.0.7. 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
failed-comparisons-3.10-3.9-c035599b822cea35d71ef86a61d4048f66cd816d
116 MB
sha256:af5642cef9cbf9bf6ac4121e79e99fe929bea2f65272cf0566b1907eb0e465cc
failed-comparisons-3.12-3.10-c035599b822cea35d71ef86a61d4048f66cd816d
116 MB
sha256:7f10828ac9b4bf79db4381308c2fe53afc36c0c951a19fa74da1ad10a9bb76ea
failed-comparisons-3.14-3.10-c035599b822cea35d71ef86a61d4048f66cd816d
116 MB
sha256:8e15299c917f90c0e63eec69977e230a6a68ff5a56beefb94a3c1305f50d55c9