Skip to content

feat: Add metadata-only replace API to Table for REPLACE snapshot operations #8124

feat: Add metadata-only replace API to Table for REPLACE snapshot operations

feat: Add metadata-only replace API to Table for REPLACE snapshot operations #8124

Triggered via pull request March 28, 2026 02:26
Status Failure
Total duration 17m 11s
Artifacts 4

python-ci.yml

on: pull_request
integration-test
16m 36s
integration-test
integration-test-s3
7m 4s
integration-test-s3
integration-test-adls
7m 30s
integration-test-adls
integration-test-gcs
6m 52s
integration-test-gcs
cibw-dev-env-smoke-test
27s
cibw-dev-env-smoke-test
Matrix: lint-and-unit-test
integration-coverage-report
30s
integration-coverage-report
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 4 warnings
lint-and-unit-test (3.10)
Process completed with exit code 2.
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)
Process completed with exit code 2.
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.
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.
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. 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/
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. 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/
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. 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/
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. 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/

Artifacts

Produced during runtime
Name Size Digest
coverage-adls
8.02 KB
sha256:519f979c790b20c8f78d45fec63f08bced9c4ae1c184298acd0d6659bfedcfd4
coverage-gcs
8.01 KB
sha256:f4aca6ac30b7d1252724e7eeebd996f304553b9dd9b0f7c8402f4c420f043dc2
coverage-integration
8.89 KB
sha256:e6a11e5867cc6e74048b5dd3a51c07432663c68baf53ffee41c52049bb69c04a
coverage-s3
8 KB
sha256:036a1a7906e69a16bed62c5931332e5c92774309506dbf3a4e6ee0d85d1c2e2e