Build: Bump datafusion from 51.0.0 to 52.3.0 #8014
python-ci.yml
on: pull_request
integration-test
11m 25s
integration-test-s3
1m 32s
integration-test-adls
1m 30s
integration-test-gcs
1m 23s
cibw-dev-env-smoke-test
45s
Matrix: lint-and-unit-test
integration-coverage-report
30s
Annotations
7 errors and 7 warnings
|
lint-and-unit-test (3.10)
Process completed with exit code 2.
|
|
lint-and-unit-test (3.13)
The strategy configuration was canceled because "lint-and-unit-test._3_10" failed
|
|
lint-and-unit-test (3.13)
The operation was canceled.
|
|
lint-and-unit-test (3.12)
The strategy configuration was canceled because "lint-and-unit-test._3_10" failed
|
|
lint-and-unit-test (3.12)
The operation was canceled.
|
|
lint-and-unit-test (3.11)
The strategy configuration was canceled because "lint-and-unit-test._3_10" failed
|
|
lint-and-unit-test (3.11)
The operation was canceled.
|
|
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/
|
|
integration-test-gcs
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-unknown-linux-gnu-ubuntu-24.04-3.12.13-pruned-ee88c43a13cab50f19c9e4d88cfbdb7c349ea3a81e3a3b9539649bf1144c1b80, another job may be creating this cache.
|
|
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-adls
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-unknown-linux-gnu-ubuntu-24.04-3.12.13-pruned-ee88c43a13cab50f19c9e4d88cfbdb7c349ea3a81e3a3b9539649bf1144c1b80, another job may be creating this cache.
|
|
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-s3
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-unknown-linux-gnu-ubuntu-24.04-3.12.13-pruned-ee88c43a13cab50f19c9e4d88cfbdb7c349ea3a81e3a3b9539649bf1144c1b80, another job may be creating this cache.
|
|
integration-test
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
|
7.99 KB |
sha256:3a5d32d604c2fd2d15e61121772be2f7e3bf82165bd4791800aa181e0f2a2182
|
|
|
coverage-gcs
|
7.99 KB |
sha256:6f701f79594494f0602cc9fa48a8898e255f9decac9fe2b18c2711c1282b16de
|
|
|
coverage-integration
|
8.87 KB |
sha256:5d05d66923aa0820bb0126b7213e142487e902fc9f2609fa53a1134b815fdd30
|
|
|
coverage-s3
|
7.98 KB |
sha256:06f27ec4aaf8b177ad718559a9e50c0a190efc12ff48b674e0b043c65aedbbea
|
|