test postgres and duckdb

corrects version strings in requirements #1038

Sign in to view logs

Re-run triggered September 28, 2024 18:32

#571

fix/correct-requirements-file-format

Status Failure

Total duration 54m 35s

Artifacts –

test_on_local_destinations.yml

on: pull_request

get_changed_sources / get_changed_sources

Matrix: test destinations postgres and duckdb

Annotations

1 error and 5 warnings

test destinations postgres and duckdb (macos-latest)

Process completed with exit code 1.

get_changed_sources / get_changed_sources

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

test destinations postgres and duckdb (windows-latest)

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

test destinations postgres and duckdb (windows-latest)

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

test destinations postgres and duckdb (macos-latest)

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

test destinations postgres and duckdb (macos-latest)

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/