Skip to content

Merge remote-tracking branch 'origin/develop' into feature/option-app… #2405

Merge remote-tracking branch 'origin/develop' into feature/option-app…

Merge remote-tracking branch 'origin/develop' into feature/option-app… #2405

Triggered via push May 29, 2026 08:10
Status Failure
Total duration 39m 43s
Artifacts 5

ci.yml

on: push
Matrix: Core / Unit Test Pipeline
Matrix: Petals Compatibility / Unit Test Pipeline
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 28 warnings
Petals Compatibility / Unit Test Pipeline (3.11)
Process completed with exit code 2.
Petals Compatibility / Unit Test Pipeline (3.12)
Process completed with exit code 2.
Petals Compatibility / Unit Test Pipeline (3.10)
The job has exceeded the maximum execution time of 20m0s
Petals Compatibility / Unit Test Pipeline (3.10)
The operation was canceled.
Core / Unit Test Pipeline (3.11)
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/upload-artifact@v4, mamba-org/setup-micromamba@v1. 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/
Core / Unit Test Pipeline (3.11)
Input 'junit_files' has been deprecated with message: Use "files" option instead.
Core / Unit Test Pipeline (3.11)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0SkoZagAAAACqplHZyTxPSIz+nHit6QOFTEFYRURHRTE3MTQARWRnZQ==
Core / Unit Test Pipeline (3.11)
Failed to restore: Cache service responded with 400
Core / Unit Test Pipeline (3.12)
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/upload-artifact@v4, mamba-org/setup-micromamba@v1. 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/
Core / Unit Test Pipeline (3.12)
Input 'junit_files' has been deprecated with message: Use "files" option instead.
Core / Unit Test Pipeline (3.12)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0S0oZagAAAADb74LshshjTrZoxCZGWwtxUEhMMzBFREdFMDIyMQBFZGdl
Core / Unit Test Pipeline (3.12)
Failed to restore: Cache service responded with 400
Core / Unit Test Pipeline (3.10)
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/upload-artifact@v4, mamba-org/setup-micromamba@v1. 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/
Core / Unit Test Pipeline (3.10)
Input 'junit_files' has been deprecated with message: Use "files" option instead.
Core / Unit Test Pipeline (3.10)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>02EwZagAAAAD/S+RmzSYFSYqlWkm3vNR7V1NURURHRTA1MTgARWRnZQ==
Core / Unit Test Pipeline (3.10)
Failed to restore: Cache service responded with 400
Petals Compatibility / Unit Test Pipeline (3.11)
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/upload-artifact@v4, mamba-org/setup-micromamba@v1. 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/
Petals Compatibility / Unit Test Pipeline (3.11)
Input 'junit_files' has been deprecated with message: Use "files" option instead.
Petals Compatibility / Unit Test Pipeline (3.11)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0204ZagAAAADA6poq7Zq5SpcwDErKSTBvTVNQMzExMDAwMTA4MDMxAEVkZ2U=
Petals Compatibility / Unit Test Pipeline (3.11)
Failed to restore: Cache service responded with 400
Petals Compatibility / Unit Test Pipeline (3.12)
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/upload-artifact@v4, mamba-org/setup-micromamba@v1. 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/
Petals Compatibility / Unit Test Pipeline (3.12)
Input 'junit_files' has been deprecated with message: Use "files" option instead.
Petals Compatibility / Unit Test Pipeline (3.12)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>04E4ZagAAAABsvG+Th8aJQqMEiylcCx7dUEhYMzFFREdFMDYxMQBFZGdl
Petals Compatibility / Unit Test Pipeline (3.12)
Failed to restore: Cache service responded with 400
Petals Compatibility / Unit Test Pipeline (3.10)
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/upload-artifact@v4, mamba-org/setup-micromamba@v1. 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/
Petals Compatibility / Unit Test Pipeline (3.10)
No files were found with the provided path: climada_petals/coverage/. No artifacts will be uploaded.
Petals Compatibility / Unit Test Pipeline (3.10)
Could not find any JUnit XML files for climada_petals/tests_xml/tests.xml
Petals Compatibility / Unit Test Pipeline (3.10)
Input 'junit_files' has been deprecated with message: Use "files" option instead.
Petals Compatibility / Unit Test Pipeline (3.10)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0GVIZagAAAAAwlNiGoYemQ4MUPtzpwbsCUEhMMzBFREdFMDQxMQBFZGdl
Petals Compatibility / Unit Test Pipeline (3.10)
Failed to restore: Cache service responded with 400

Artifacts

Produced during runtime
Name Size Digest
coverage-report-core-unittests-py3.10
1.37 MB
sha256:4413046c865b5721bae4cc083042b1f1189db50c5a6d63b8b7aebfd3fc7a5375
coverage-report-core-unittests-py3.11
1.37 MB
sha256:a62e09ea3b8b249acddda576f7bf194b20e51afc60d7c34c9e0b807d26674444
coverage-report-core-unittests-py3.12
1.37 MB
sha256:ab9ed2a57747128d0560edfade42189c52ba6a46af5b4818579ccea817627c94
coverage-report-petals-unittests-py3.11
660 KB
sha256:e9ae0eab11f4706e84dccf79faaa92f8f7b56eebb1b199c112581900f30d9d30
coverage-report-petals-unittests-py3.12
662 KB
sha256:c74cc817607a33ebba20211e6bddbe45d99b4f90d1a9d95f9ee841b9fe18e873