Skip to content

updated cibuildwheel and codecov upload actions, #1101

updated cibuildwheel and codecov upload actions,

updated cibuildwheel and codecov upload actions, #1101

Triggered via push May 10, 2026 22:52
Status Failure
Total duration 29m 27s
Artifacts

ci-build.yml

on: push
Test SpiceyPy Pyodide build
4m 9s
Test SpiceyPy Pyodide build
Test SpiceyPy Conda install
1m 48s
Test SpiceyPy Conda install
Matrix: Test SpiceyPy 🌶️ 🥧
Fit to window
Zoom out
Zoom in

Annotations

2 errors, 3 warnings, and 3 notices
Test SpiceyPy Pyodide build
Process completed with exit code 1.
Test SpiceyPy Pyodide build
cibuildwheel: Command ['/tmp/cibw-run-72hcxdb7/cp313-pyodide_wasm32/venv-test/bin/pip', 'install', '/tmp/cibw-run-72hcxdb7/cp313-pyodide_wasm32/repaired_wheel/spiceypy-8.1.0-cp313-cp313-pyodide_2025_0_wasm32.whl'] failed with code 1.
Test SpiceyPy 🌶️ 🥧 (windows-latest, 3.14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/[email protected]. 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/
Test SpiceyPy 🌶️ 🥧 (windows-latest, 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/[email protected]. 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/
Test SpiceyPy 🌶️ 🥧 (windows-latest, 3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/[email protected]. 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/
Test SpiceyPy 🌶️ 🥧 (windows-latest, 3.14)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Test SpiceyPy 🌶️ 🥧 (windows-latest, 3.12)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Test SpiceyPy 🌶️ 🥧 (windows-latest, 3.13)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026