Skip to content

Add env variables to configure manifest cache #7998

Add env variables to configure manifest cache

Add env variables to configure manifest cache #7998

Triggered via pull request March 13, 2026 04:11
Status Cancelled
Total duration 5m 26s
Artifacts 3

python-ci.yml

on: pull_request
integration-test
5m 22s
integration-test
integration-test-s3
1m 14s
integration-test-s3
integration-test-adls
1m 9s
integration-test-adls
integration-test-gcs
1m 22s
integration-test-gcs
cibw-dev-env-smoke-test
26s
cibw-dev-env-smoke-test
Matrix: lint-and-unit-test
integration-coverage-report
integration-coverage-report
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 3 warnings
integration-test
Canceling since a higher priority waiting request for Python CI-refs/pull/2993/merge exists
integration-test
The operation was canceled.
Python CI
Canceling since a higher priority waiting request for Python CI-refs/pull/2993/merge exists
integration-test-adls
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
integration-test-s3
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
integration-test-gcs
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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
coverage-adls
8 KB
sha256:7d235c8a67e5dd530c106351a01c0403da4245b6d5a3c515245a50267d246b48
coverage-gcs
7.99 KB
sha256:ea7b935f61762851a7c8df1affc6d35564abf2d67cc4c732071b14561538d88b
coverage-s3
7.99 KB
sha256:f28b1ba51d6e0371d10dd21596ff8ee35358ea506a7667f2ad9d2c9d13d70577