Add review-4270327414 coverage #1495
sfc-gh-dachristensenpytest_all.yml
on: push
build-image-almalinux
8s
build-image-debian
5s
Matrix: build-and-install-almalinux
lint-check-18
/
lint
1m 35s
Matrix: build-and-install-debian
Matrix: test-check-pg-lake-table
Matrix: test-check
Matrix: test-isolation
Matrix: test-upgrade
Matrix: test-installcheck-pg-lake-table
Matrix: test-installcheck-postgres
Matrix: test-installcheck
Annotations
58 errors and 71 warnings
|
test-upgrade (16-17, check-pg_lake_table-upgrade)
Canceling since a higher priority waiting request for refs/heads/pgguru/duckdb-quote-identifier exists
|
|
test-installcheck-postgres (17, installcheck-postgres)
Canceling since a higher priority waiting request for refs/heads/pgguru/duckdb-quote-identifier exists
|
|
test-installcheck-postgres (17, installcheck-postgres)
The operation was canceled.
|
|
test-check (17, check-pg_extension_base)
Canceling since a higher priority waiting request for refs/heads/pgguru/duckdb-quote-identifier exists
|
|
test-check (17, check-pgduck_server)
Canceling since a higher priority waiting request for refs/heads/pgguru/duckdb-quote-identifier exists
|
|
test-check (17, check-pgduck_server)
The operation was canceled.
|
|
test-check (17, check-pg_lake_spatial)
Canceling since a higher priority waiting request for refs/heads/pgguru/duckdb-quote-identifier exists
|
|
test-check (18, check-pg_lake_benchmark)
Canceling since a higher priority waiting request for refs/heads/pgguru/duckdb-quote-identifier exists
|
|
test-check (18, check-pg_lake_benchmark)
The operation was canceled.
|
|
test-check-pg-lake-table (18, check-pg_lake_table, 4)
Canceling since a higher priority waiting request for refs/heads/pgguru/duckdb-quote-identifier exists
|
|
test-check-pg-lake-table (18, check-pg_lake_table, 4)
The operation was canceled.
|
|
test-installcheck-postgres (18, installcheck-postgres)
Canceling since a higher priority waiting request for refs/heads/pgguru/duckdb-quote-identifier exists
|
|
test-check-pg-lake-table (18, check-pg_lake_table, 1)
Canceling since a higher priority waiting request for refs/heads/pgguru/duckdb-quote-identifier exists
|
|
test-check-pg-lake-table (18, check-pg_lake_table, 1)
The operation was canceled.
|
|
test-check-pg-lake-table (17, check-pg_lake_table, 5)
Canceling since a higher priority waiting request for refs/heads/pgguru/duckdb-quote-identifier exists
|
|
test-check-pg-lake-table (17, check-pg_lake_table, 5)
The operation was canceled.
|
|
test-check-pg-lake-table (17, check-pg_lake_table, 1)
Canceling since a higher priority waiting request for refs/heads/pgguru/duckdb-quote-identifier exists
|
|
test-check-pg-lake-table (17, check-pg_lake_table, 1)
The operation was canceled.
|
|
test-check (18, check-pgduck_server)
Canceling since a higher priority waiting request for refs/heads/pgguru/duckdb-quote-identifier exists
|
|
test-check (18, check-pgduck_server)
The operation was canceled.
|
|
test-check-pg-lake-table (17, check-pg_lake_table, 3)
Canceling since a higher priority waiting request for refs/heads/pgguru/duckdb-quote-identifier exists
|
|
test-check-pg-lake-table (18, check-pg_lake_table, 3)
Canceling since a higher priority waiting request for refs/heads/pgguru/duckdb-quote-identifier exists
|
|
test-check-pg-lake-table (17, check-pg_lake_table, 3)
The operation was canceled.
|
|
test-check-pg-lake-table (18, check-pg_lake_table, 3)
The operation was canceled.
|
|
test-check (18, check-avro)
Canceling since a higher priority waiting request for refs/heads/pgguru/duckdb-quote-identifier exists
|
|
test-check (18, check-avro)
The operation was canceled.
|
|
test-check (17, check-pg_lake_iceberg)
Canceling since a higher priority waiting request for refs/heads/pgguru/duckdb-quote-identifier exists
|
|
test-check (17, check-pg_lake_iceberg)
The operation was canceled.
|
|
test-check (18, check-pg_lake_copy)
Canceling since a higher priority waiting request for refs/heads/pgguru/duckdb-quote-identifier exists
|
|
test-check (18, check-pg_lake_copy)
The operation was canceled.
|
|
test-check-pg-lake-table (17, check-pg_lake_table, 2)
Canceling since a higher priority waiting request for refs/heads/pgguru/duckdb-quote-identifier exists
|
|
test-check-pg-lake-table (17, check-pg_lake_table, 2)
The operation was canceled.
|
|
test-check (17, check-avro)
Canceling since a higher priority waiting request for refs/heads/pgguru/duckdb-quote-identifier exists
|
|
test-check (17, check-avro)
The operation was canceled.
|
|
test-check (17, check-pg_lake_benchmark)
Canceling since a higher priority waiting request for refs/heads/pgguru/duckdb-quote-identifier exists
|
|
test-check (17, check-pg_lake_benchmark)
The operation was canceled.
|
|
test-check-pg-lake-table (18, check-pg_lake_table, 2)
Canceling since a higher priority waiting request for refs/heads/pgguru/duckdb-quote-identifier exists
|
|
test-check-pg-lake-table (18, check-pg_lake_table, 2)
The operation was canceled.
|
|
test-check-pg-lake-table (17, check-pg_lake_table, 4)
Canceling since a higher priority waiting request for refs/heads/pgguru/duckdb-quote-identifier exists
|
|
test-check-pg-lake-table (17, check-pg_lake_table, 4)
The operation was canceled.
|
|
test-check-pg-lake-table (18, check-pg_lake_table, 5)
Canceling since a higher priority waiting request for refs/heads/pgguru/duckdb-quote-identifier exists
|
|
test-check-pg-lake-table (18, check-pg_lake_table, 5)
The operation was canceled.
|
|
test-check (18, check-pg_lake_iceberg)
Canceling since a higher priority waiting request for refs/heads/pgguru/duckdb-quote-identifier exists
|
|
test-check (18, check-pg_lake_iceberg)
The operation was canceled.
|
|
test-installcheck (16, installcheck-pgduck_server)
Canceling since a higher priority waiting request for refs/heads/pgguru/duckdb-quote-identifier exists
|
|
test-installcheck-pg-lake-table (16, installcheck-pg_lake_table, 3)
Canceling since a higher priority waiting request for refs/heads/pgguru/duckdb-quote-identifier exists
|
|
test-installcheck-pg-lake-table (16, installcheck-pg_lake_table, 3)
The operation was canceled.
|
|
test-installcheck-postgres (16, installcheck-postgres-with_extensions_created)
Canceling since a higher priority waiting request for refs/heads/pgguru/duckdb-quote-identifier exists
|
|
test-installcheck-postgres (16, installcheck-postgres-with_extensions_created)
The operation was canceled.
|
|
test-installcheck-pg-lake-table (16, installcheck-pg_lake_table, 2)
Canceling since a higher priority waiting request for refs/heads/pgguru/duckdb-quote-identifier exists
|
|
test-installcheck-pg-lake-table (16, installcheck-pg_lake_table, 5)
Canceling since a higher priority waiting request for refs/heads/pgguru/duckdb-quote-identifier exists
|
|
test-installcheck-postgres (18, installcheck-postgres-with_extensions_created)
Canceling since a higher priority waiting request for refs/heads/pgguru/duckdb-quote-identifier exists
|
|
test-installcheck-pg-lake-table (16, installcheck-pg_lake_table, 2)
The operation was canceled.
|
|
test-installcheck-pg-lake-table (16, installcheck-pg_lake_table, 5)
The operation was canceled.
|
|
test-installcheck-postgres (18, installcheck-postgres-with_extensions_created)
The operation was canceled.
|
|
test-installcheck-pg-lake-table (16, installcheck-pg_lake_table, 4)
Canceling since a higher priority waiting request for refs/heads/pgguru/duckdb-quote-identifier exists
|
|
test-installcheck-pg-lake-table (16, installcheck-pg_lake_table, 4)
The operation was canceled.
|
|
Build and run all tests
Canceling since a higher priority waiting request for refs/heads/pgguru/duckdb-quote-identifier exists
|
|
build-image-debian
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/login-action@v2. 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/
|
|
build-image-almalinux
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/login-action@v2. 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/
|
|
lint-check-18 / lint
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build-and-install-debian (18)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, 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/
|
|
build-and-install-debian (17)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, 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/
|
|
build-and-install-almalinux (18)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, 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/
|
|
build-and-install-almalinux (16)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, 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/
|
|
build-and-install-debian (16)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, 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/
|
|
build-and-install-almalinux (17)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, 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/
|
|
test-installcheck (16, installcheck-pg_extension_base)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-check (18, check-duckdb_pglake)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-check (18, check-duckdb_pglake)
No files were found with the provided path: /tmp/pg_lake_tests/logfile
/tmp/pg_installcheck_tests/logfile
/tmp/pytest-of-*/**/postgres*.log. No artifacts will be uploaded.
|
|
test-check (17, check-duckdb_pglake)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-check (17, check-duckdb_pglake)
No files were found with the provided path: /tmp/pg_lake_tests/logfile
/tmp/pg_installcheck_tests/logfile
/tmp/pytest-of-*/**/postgres*.log. No artifacts will be uploaded.
|
|
test-check (17, check-pg_map)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-isolation (18, check-isolation_pg_lake_table)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-isolation (18, check-isolation_pg_lake_table)
No files were found with the provided path: /tmp/pg_lake_tests/logfile
/tmp/pg_installcheck_tests/logfile
/tmp/pytest-of-*/**/postgres*.log. No artifacts will be uploaded.
|
|
test-check (18, check-pg_map)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-check (18, check-pg_lake)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-installcheck (16, installcheck-pg_lake)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-upgrade (16-18, check-pg_lake_table-upgrade)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-check (18, check-pg_extension_base)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-check (17, check-pg_lake)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-installcheck-postgres (17, installcheck-postgres-with_extensions_created)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-installcheck (16, installcheck-pg_lake_copy)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-installcheck (16, installcheck-pg_map)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-check (17, check-pg_lake_copy)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-isolation (17, check-isolation_pg_lake_table)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-isolation (17, check-isolation_pg_lake_table)
No files were found with the provided path: /tmp/pg_lake_tests/logfile
/tmp/pg_installcheck_tests/logfile
/tmp/pytest-of-*/**/postgres*.log. No artifacts will be uploaded.
|
|
test-installcheck (16, installcheck-pg_lake_benchmark)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-installcheck-postgres (16, installcheck-postgres)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-installcheck-pg-lake-table (16, installcheck-pg_lake_table, 1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-check (18, check-pg_lake_spatial)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-installcheck (16, installcheck-pg_lake_spatial)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-upgrade (17-18, check-pg_lake_table-upgrade)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-installcheck (16, installcheck-pg_lake_iceberg)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-upgrade (16-17, check-pg_lake_table-upgrade)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-installcheck-postgres (17, installcheck-postgres)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-check (17, check-pg_extension_base)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-check (17, check-pgduck_server)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-check (17, check-pg_lake_spatial)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-check (18, check-pg_lake_benchmark)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-check-pg-lake-table (18, check-pg_lake_table, 4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-installcheck-postgres (18, installcheck-postgres)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-check-pg-lake-table (18, check-pg_lake_table, 1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-check-pg-lake-table (17, check-pg_lake_table, 5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-check-pg-lake-table (17, check-pg_lake_table, 1)
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/download-artifact@v4, 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/
|
|
test-check-pg-lake-table (17, check-pg_lake_table, 1)
No files were found with the provided path: /tmp/pg_lake_tests/logfile
/tmp/pg_installcheck_tests/logfile
/tmp/pytest-of-*/**/postgres*.log. No artifacts will be uploaded.
|
|
test-check (18, check-pgduck_server)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-check (18, check-pgduck_server)
No files were found with the provided path: /tmp/pg_lake_tests/logfile
/tmp/pg_installcheck_tests/logfile
/tmp/pytest-of-*/**/postgres*.log. No artifacts will be uploaded.
|
|
test-check-pg-lake-table (17, check-pg_lake_table, 3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-check-pg-lake-table (18, check-pg_lake_table, 3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-check (18, check-avro)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-check (18, check-avro)
No files were found with the provided path: /tmp/pg_lake_tests/logfile
/tmp/pg_installcheck_tests/logfile
/tmp/pytest-of-*/**/postgres*.log. No artifacts will be uploaded.
|
|
test-check (17, check-pg_lake_iceberg)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-check (18, check-pg_lake_copy)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-check-pg-lake-table (17, check-pg_lake_table, 2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-check (17, check-avro)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-check (17, check-avro)
No files were found with the provided path: /tmp/pg_lake_tests/logfile
/tmp/pg_installcheck_tests/logfile
/tmp/pytest-of-*/**/postgres*.log. No artifacts will be uploaded.
|
|
test-check (17, check-pg_lake_benchmark)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-check-pg-lake-table (18, check-pg_lake_table, 2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-check-pg-lake-table (17, check-pg_lake_table, 4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-check-pg-lake-table (18, check-pg_lake_table, 5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-check (18, check-pg_lake_iceberg)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-installcheck (16, installcheck-pgduck_server)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-installcheck-pg-lake-table (16, installcheck-pg_lake_table, 3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-installcheck-postgres (16, installcheck-postgres-with_extensions_created)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-installcheck-pg-lake-table (16, installcheck-pg_lake_table, 2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-installcheck-pg-lake-table (16, installcheck-pg_lake_table, 5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-installcheck-postgres (18, installcheck-postgres-with_extensions_created)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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/
|
|
test-installcheck-pg-lake-table (16, installcheck-pg_lake_table, 4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, 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 | |
|---|---|---|---|
|
avro-almalinux-artifacts
Expired
|
3.01 MB |
sha256:0aa01fd567a0682d072c6e92a8d2db3d938e466c0227da56e0198b9ff88ee80a
|
|
|
avro-debian-artifacts
Expired
|
3 MB |
sha256:f19f52831f99741d51e1496a5c2b2dc520650407d49d9d38bb1c8588ad4df9e5
|
|
|
postgres-16-almalinux-artifacts
Expired
|
364 MB |
sha256:9dfc6238c4d2474ab2e6012f6fc8e31375577d2a6afcccf784487a6c4f050506
|
|
|
postgres-16-debian-artifacts
Expired
|
365 MB |
sha256:be049961d7a0766233f2e75d9fdc2324abcd1accb6a8c9d88e7ba38c8eb1a15a
|
|
|
postgres-17-almalinux-artifacts
Expired
|
365 MB |
sha256:1e6afed01b5477801c512ee00afdde03907b2d0d19c67548b373b392827e79b8
|
|
|
postgres-17-debian-artifacts
Expired
|
366 MB |
sha256:9661f2ebc7229b263fee04af05c2dad7591990abc0e4c8b9d9432ffac2c9b56c
|
|
|
postgres-18-almalinux-artifacts
Expired
|
369 MB |
sha256:00dadebab36eb0817bbf1b8be46e450c4dae19319091beb2f8fe97bb84893886
|
|
|
postgres-18-debian-artifacts
Expired
|
370 MB |
sha256:d738e998e619a2620479ecaef2f3d9a81939cf168cbbe561309519da51159bd4
|
|
|
postgres-logs-16-installcheck-pg_extension_base
Expired
|
9.78 KB |
sha256:51fe2e55d2351596a7b39cb3e6c23cc29d38ba919be4f7c593e2bbfff27d70b2
|
|
|
postgres-logs-16-installcheck-pg_lake
Expired
|
1.56 KB |
sha256:290514e6276c286fe673d9653161d3c467f55ac95c34c8a466a3aa4f7cb73240
|
|
|
postgres-logs-16-installcheck-pg_lake_benchmark
Expired
|
130 KB |
sha256:38ba26f54fda864da178c7e7b0ff4e74b6adeea6f6fe8d372bd5f8c6c04ceef5
|
|
|
postgres-logs-16-installcheck-pg_lake_copy
Expired
|
43 KB |
sha256:6849accd0ca6a060db703e17593a99f120985717428b5832e0c1817932c1b574
|
|
|
postgres-logs-16-installcheck-pg_lake_iceberg
Expired
|
310 KB |
sha256:0aeafc06c957c2c26071a0985b9b0bcb52a23cd79d00b5cf79e61e70ecb74981
|
|
|
postgres-logs-16-installcheck-pg_lake_spatial
Expired
|
43 KB |
sha256:c3f727e72236db8e2caa75d0727d6ff5c67b17ab09708f1b7f3bfa405fb14516
|
|
|
postgres-logs-16-installcheck-pg_lake_table-1
Expired
|
177 KB |
sha256:d900beadd1d07f61c906fcd8e8bb8b44133a155fdfc178ff7b0efa24616bfe73
|
|
|
postgres-logs-16-installcheck-pg_lake_table-2
Expired
|
102 KB |
sha256:4a1c1d5b99c7cb99fe455f9d0e9b507fb3862370e2b8eb82647594eaa4faf918
|
|
|
postgres-logs-16-installcheck-pg_lake_table-3
Expired
|
432 KB |
sha256:3985d92c6262add2704ab42ba844bf44bdb9cbf8a9a52d03a67f5c7667f97b9b
|
|
|
postgres-logs-16-installcheck-pg_lake_table-4
Expired
|
144 KB |
sha256:496ddbbf68fcf0fdec3824b4a66d30a6ae44b7d043a8e5002f8036a0357b39fd
|
|
|
postgres-logs-16-installcheck-pg_lake_table-5
Expired
|
243 KB |
sha256:9501e0881d8a48869befc8609dddb2b2774afb6e070cecc42693894e5cdff8fb
|
|
|
postgres-logs-16-installcheck-pg_map
Expired
|
2.75 KB |
sha256:0c0111da43e22b3397ebc9ab07cada01db49cdedc9267e4ef7cf89418d4e2757
|
|
|
postgres-logs-16-installcheck-pgduck_server
Expired
|
4.31 KB |
sha256:bb0a239d54ed46e60780dc063811a772cbdcae7e2a67641e349ba3b72cae6fbf
|
|
|
postgres-logs-16-installcheck-postgres
Expired
|
1.34 MB |
sha256:3fbc1e27e4e4e6b406926543ff40769a8d422c7b9c4db6212495726a912a037a
|
|
|
postgres-logs-16-installcheck-postgres-with_extensions_created
Expired
|
434 KB |
sha256:37e7458b6645984ebe3fe31c177370da44ddf399e251e9498c4dadfe5d852e95
|
|
|
postgres-logs-17-check-pg_extension_base
Expired
|
4.49 KB |
sha256:6ab84f5296a73e1a72106d1eb8308b6b32dfa67882622331e5eafb989b4fdd87
|
|
|
postgres-logs-17-check-pg_lake
Expired
|
1.39 KB |
sha256:3547d998cd0ee7ee3b256e87adc55234867ce2225ede6ff97dcfb59b1672fd42
|
|
|
postgres-logs-17-check-pg_lake_benchmark
Expired
|
10.3 KB |
sha256:b91a675c567686db7747b625d168bcf89047ede6742fe5e0ab49d6b56a2e0da9
|
|
|
postgres-logs-17-check-pg_lake_copy
Expired
|
11.5 KB |
sha256:06b1f5af536d66b5ee661840668620a52f1b7ce61dd3bfa52877bcc0ecd3f208
|
|
|
postgres-logs-17-check-pg_lake_iceberg
Expired
|
119 KB |
sha256:39aa1cf14858b9880ff1720e547b2e4df994d4ffbbdfc20a4d059ae4355d92e1
|
|
|
postgres-logs-17-check-pg_lake_spatial
Expired
|
532 KB |
sha256:3e41b7d3a58fb2ad2fb53f7270dc3c823a823df7df877ac84388d46676d9e133
|
|
|
postgres-logs-17-check-pg_lake_table-2
Expired
|
10.2 KB |
sha256:37bd9deb5cf66a33748d0ef5a5df29f987ae5330f39e864a4355325cc347ca47
|
|
|
postgres-logs-17-check-pg_lake_table-3
Expired
|
46.6 KB |
sha256:c250f40ea92245a9924aa304d5e7d38c9797dfa059e808ca3d30ba37b8988a32
|
|
|
postgres-logs-17-check-pg_lake_table-4
Expired
|
7.96 KB |
sha256:d0a617f5c4cd91967869d2fe5334e015dbb9812494ebaa2f6031bf5c0ca1342e
|
|
|
postgres-logs-17-check-pg_lake_table-5
Expired
|
33.9 KB |
sha256:658f426771fabdabad5a80c632d99db31c0e50988059eadbc9a5b6bcbd20f481
|
|
|
postgres-logs-17-check-pg_lake_table-upgrade-from16
Expired
|
3.03 KB |
sha256:8bf5b9142b37330866f62763cb532f092b00ffccf7f29ac52c779c8018148011
|
|
|
postgres-logs-17-check-pg_map
Expired
|
1.51 KB |
sha256:7cad35365b95f77c659381229896540e87ac9345ff6ce6bac22e7990a9fe31ae
|
|
|
postgres-logs-17-check-pgduck_server
Expired
|
1013 Bytes |
sha256:a6d66cab430424d43af47e9c9eda2de3e804b69f2f3a189a7b43bbbf334357cd
|
|
|
postgres-logs-17-installcheck-postgres
Expired
|
1.29 MB |
sha256:7723b110553f4f428b65b4edd5863c3e419f571633cff1aa9134ee45a1fe1d2a
|
|
|
postgres-logs-17-installcheck-postgres-with_extensions_created
Expired
|
1.59 MB |
sha256:aaed897875aa947774b5abf11287d155ff09bc1cf006b60188029097caecd14b
|
|
|
postgres-logs-18-check-pg_extension_base
Expired
|
4.54 KB |
sha256:1243323b376f057c681e81f3dc1bb1baa1d13da8e5f06cf3d16d79b03f8c8c0b
|
|
|
postgres-logs-18-check-pg_lake
Expired
|
1.41 KB |
sha256:c039c40836350c18a814922dbf3011faac3f6e4191599dbc51326631ae2692c0
|
|
|
postgres-logs-18-check-pg_lake_benchmark
Expired
|
23.2 KB |
sha256:206bbeb432cb42f7a1d3c3aa612ec4bb65d3e41696eb5174ce4307fbed798a89
|
|
|
postgres-logs-18-check-pg_lake_copy
Expired
|
6.25 KB |
sha256:3d8b31c12df4bbc36966230ba660c28a8e8d6d65b77e54bba5d864308ae8e7d5
|
|
|
postgres-logs-18-check-pg_lake_iceberg
Expired
|
108 KB |
sha256:ead4cde87e26c4a591e33060670cc057166aa795bc79841dbc39d01141fe35f4
|
|
|
postgres-logs-18-check-pg_lake_spatial
Expired
|
1000 KB |
sha256:89ca9c61fd8995bcc4dd0c86765993dc1b269527c6e1fc6c5c0325f653ef7d4b
|
|
|
postgres-logs-18-check-pg_lake_table-1
Expired
|
26.5 KB |
sha256:f72a3760161dbfeee72d0e5fda790adab1308bfab4ee03dcfed4d97640925171
|
|
|
postgres-logs-18-check-pg_lake_table-2
Expired
|
12.7 KB |
sha256:30fb8b392fba6c205d0c365eb3422334eed074cb977d04e4d386dd46a60241b8
|
|
|
postgres-logs-18-check-pg_lake_table-3
Expired
|
38.8 KB |
sha256:ea42385da0f0422c97e132c2f7be1a801b32bb32fdaa89dd8c7dd6d9ec28a5bb
|
|
|
postgres-logs-18-check-pg_lake_table-4
Expired
|
8.9 KB |
sha256:002f05a9773c9d432e7f8e3eb5aa7c6e406dd5e5c6dd56447fc91a791d47603e
|
|
|
postgres-logs-18-check-pg_lake_table-5
Expired
|
46 KB |
sha256:07e48d83de722afa99132fa9f12ed9ed24ece859a1b6ddd4a27ac4bf04551d72
|
|
|
postgres-logs-18-check-pg_lake_table-upgrade-from16
Expired
|
3.06 KB |
sha256:b01c9881a994384c21d0f3b26f837e04d14509fed4521fb04ea4be0e06acd684
|
|
|
postgres-logs-18-check-pg_lake_table-upgrade-from17
Expired
|
3.05 KB |
sha256:4d9287aa4edeb8a9ec2dcb5bd58a898ada57912a5131e0d9c5f6d3e6b9947daa
|
|
|
postgres-logs-18-check-pg_map
Expired
|
1.52 KB |
sha256:8d8b28cf0397af725128a544072a4e8009c293bfaa11f15ac5dbc6e08c4d468e
|
|
|
postgres-logs-18-installcheck-postgres
Expired
|
1.63 MB |
sha256:94fd37733f725ee8a751b8b7fda97eada39a13d4f4c1b851ba934c3cc99bfb22
|
|
|
postgres-logs-18-installcheck-postgres-with_extensions_created
Expired
|
167 KB |
sha256:cc8160bea49560a5323d032a17b208bbd4e9315e66c4624b640b99568da7fd70
|
|