Skip to content
GitHub CI

return an ImpactFreqCurve object when inter- extrapolating #2266

Sign in to view logs

return an ImpactFreqCurve object when inter- extrapolating

return an ImpactFreqCurve object when inter- extrapolating #2266

Triggered via push April 1, 2026 14:53
@ValentinGebhartValentinGebhart
pushed 36d4cc8
feature/interpolate_exceedance
Status Failure
Total duration 40m 18s
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

3 errors and 27 warnings
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>0yTHNaQAAAAAXMF0MI0ijQKXbDLzP0xMQUEhMMzBFREdFMDQxOQBFZGdl
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>03jHNaQAAAAAto3TyCxj+Q4kcV9/AIAG/UEFPRURHRTA1MTcARWRnZQ==
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>0ljTNaQAAAABldFK4g4bVSovZOXA8KRVWUEhYMzFFREdFMDIxNABFZGdl
Core / Unit Test Pipeline (3.10)
Failed to restore: Cache service responded with 400
test_get_data_overpass (climada_petals.entity.exposures.test.test_osm_dataloader.TestOSMApiQuery) failed: climada_petals.entity.exposures.test.test_osm_dataloader.TestOSMApiQuery#L0
climada_petals/tests_xml/tests.xml [took 2m 52s]
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>0ezbNaQAAAADyTFWwhTzwT7ILv8JA6f/dUEhMMzBFREdFMDEyMABFZGdl
Petals Compatibility / Unit Test Pipeline (3.12)
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>0hDbNaQAAAAD/lw5u7ucKR5M+Twrd7YmDUEhMMzBFREdFMDExNgBFZGdl
Petals Compatibility / Unit Test Pipeline (3.11)
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>0UDnNaQAAAAAz9VQpziccQ7V6uiKhSrhGUEhMMzBFREdFMDQyMABFZGdl
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.35 MB
sha256:9d0dff61991c4ec54f2b7206086c48a5c3ae23848db97d29af192b67d164b64b
coverage-report-core-unittests-py3.11
1.35 MB
sha256:39b8c6d95037644007dcb1fcbd1edff25498eaf3a476c4191ca19e6ddd73089f
coverage-report-core-unittests-py3.12
1.35 MB
sha256:af6f3cdf356fac64d84f3fcde9896fc79b09d5af8fafb690b1167053645a9ea7
coverage-report-petals-unittests-py3.11
660 KB
sha256:0e2bb6c6355dbee537da6d6d0f9882c2f949d3ef3ba11340abda443efa372c75
coverage-report-petals-unittests-py3.12
661 KB
sha256:b36c8fa7288a6e19cb299c643d6f5cf1e1b5fe7dca22a8556ee18cf75617294c