Skip to content
GitHub CI

Make conda-env hook not use uv #2439

Sign in to view logs

Make conda-env hook not use uv

Make conda-env hook not use uv #2439

Triggered via push June 10, 2026 09:10
@peanutfunpeanutfun
pushed 307f5ac
add-uv-config
Status Failure
Total duration 8m 1s
Artifacts 3

ci.yml

on: push
Matrix: Core / Unit Test Pipeline
Core / Integration Test Pipeline
2m 48s
Core / Integration Test Pipeline
Matrix: Petals Compatibility / Unit Test Pipeline
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 22 warnings
Core / Integration Test Pipeline
Process completed with exit code 1.
Petals Compatibility / Unit Test Pipeline (3.12)
ENOENT: no such file or directory, lstat '/home/runner/work/_temp/setup-micromamba/micromamba-shell'
Petals Compatibility / Unit Test Pipeline (3.12)
The process '/home/runner/micromamba-bin/micromamba' failed with exit code 1
Petals Compatibility / Unit Test Pipeline (3.10)
ENOENT: no such file or directory, lstat '/home/runner/work/_temp/setup-micromamba/micromamba-shell'
Petals Compatibility / Unit Test Pipeline (3.10)
The process '/home/runner/micromamba-bin/micromamba' failed with exit code 1
Petals Compatibility / Unit Test Pipeline (3.11)
ENOENT: no such file or directory, lstat '/home/runner/work/_temp/setup-micromamba/micromamba-shell'
Petals Compatibility / Unit Test Pipeline (3.11)
The process '/home/runner/micromamba-bin/micromamba' failed with exit code 1
Core / Integration Test Pipeline
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/checkout@v4, amochkin/action-json@v1. Actions will be forced to run with Node.js 24 by default starting June 16th, 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)
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/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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.12)
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/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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.10)
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/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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.
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 16th, 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)
No files were found with the provided path: climada_petals/coverage/. No artifacts will be uploaded.
Petals Compatibility / Unit Test Pipeline (3.12)
Could not find any JUnit XML files for climada_petals/tests_xml/tests.xml
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 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 16th, 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 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 16th, 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)
No files were found with the provided path: climada_petals/coverage/. No artifacts will be uploaded.
Petals Compatibility / Unit Test Pipeline (3.11)
Could not find any JUnit XML files for climada_petals/tests_xml/tests.xml
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 restore: Cache service responded with 400

Artifacts

Produced during runtime
Name Size Digest
coverage-report-core-unittests-py3.10
1.39 MB
sha256:f774f35fda2f7c400f623dc0a86f58ed04f7c29a185677ca01dea38bcef81338
coverage-report-core-unittests-py3.11
1.39 MB
sha256:fdc4cdacf4eae86aed45685e25c1bca860d483e1062016a716d1af90c42938fa
coverage-report-core-unittests-py3.12
1.4 MB
sha256:697e89fae88cf2a961faf528f45aaae38bdcefce7c5264c6ac268bad9ead95e9